docs: document procedure to migrate a live cluster to three-data-hall redundancy #2191
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
gm42
force-pushed
the
docs/3dh-migrate
branch
from
93c674b to
7c3701c
Compare
johscheuer
reviewed
Jan 15, 2025
gm42
force-pushed
the
docs/3dh-migrate
branch
from
7c3701c to
919bbb9
Compare
gm42
force-pushed
the
docs/3dh-migrate
branch
from
919bbb9 to
163ee3e
Compare
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.
Description
When using single/double/triple redundancy it is not possible to migrate a live cluster to
three_data_hallredundancy without incurring into some temporary timeouts or unavailability.This change adds the steps necessary to perform migration without incurring into these availability problems.
Type of change
Follow-up
Note: I also changed documentation of
--locality_data_hallto say that it is actually being used now