Fixed database status in multi-region mode when primary DC fails #12071
+18
−6
Conversation
This file contains hidden or 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
MarkSh1
changed the title
|
topic in foundationdb forum about this problem : link |
Sorry for the late review. Can you help to explain a bit about the built-in safeguard? Thanks! |
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.
When the primary data center (DC) in the first region becomes an unavailable in a multi-region deployment, the system automatically fails over to the secondary region if a satellite node is present in the affected region. After this transition, the database generates the following status warning:
While this warning indicates potential synchronization issues, the system's built-in safeguards prevent actual data loss during this failover process.
This PR removed phrase about the lost data.