Split Keeper replication out of ReplicatedAccessStorage for shared use#81245
Conversation
1a409a5 to
2962151
Compare
|
CI failing on master as well for Tagging issue: #81319 |
|
Here's the direct diff between |
ReplicatedAccessStorage for shared use
9669cd7 to
39eb90b
Compare
|
feels like the integration test failing is a flake. Ran locally on my branch with: and its all green: |
|
LGTM. @thevar1able, what do you think? |
thevar1able
left a comment
There was a problem hiding this comment.
LGTM.
Performance comparison failure is unrelated.
@kcmannem the failure was actually related to the changes in this PR. "It works on my machine" != "it works". |
A slight refactor for
ReplicatedAccessStorage. This decouples the replication logic into a separateZooKeeperReplicatorclass so that we can share it between other AccessStorages.Also updates the error messaging to include the Access Storage which throws the exception, to identify more clearly the source. Needed when multiple storages can use keeper replication.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Documentation entry for user-facing changes