Only run lightweight sync between replicas during restore [DDB-1415] #262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lightweight replica sync skips parts merges, part mutations, metadata alter, part cloning from other shards, and pinned part UUID sync. This should be good enough for the cluster to be in a working state, leaving the remaining work to be done asynchronously.
aris-aiven
force-pushed
the
aris-sync-lightweight
branch
from
26217ed to
3d68892
Compare
bogdanp05
previously approved these changes
Nov 27, 2024
This reverts commit 8ac07a4.
|
Why was it necessary to revert 8ac07a4 ? |
|
@Khatskevich it broke integration tests since the setup is trying to connect to Azure over an empty bucket endpoint and times out after 30s |
joelynch
approved these changes
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lightweight replica sync skips parts merges, part mutations, metadata alter, part cloning from other shards, and pinned part UUID sync. This should be good enough for the cluster to be in a working state, leaving the remaining work to be done asynchronously.