Document failovering to sync replicas only #1274
Open
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
as51340
added
status: ready
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
antejavor
approved these changes
May 19, 2025
Comment on lines
+387
to
+401
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
| Users can also choose whether failovering to async replica is allowed by using the following query: | ||
|
|
There was a problem hiding this comment.
Suggested change
| Users can also choose whether failovering to async replica is allowed by using the following query: | |
| Users can also choose whether failover to the async replica is allowed by using the following query: | |
Comment on lines
+406
to
+408
| By the default the value is true which means that only sync replicas are candidates in the election. When the value is set to false, async replica is also considered but | ||
| there is then an additional risk of experiencing a data loss. However, failovering to async replica may be necessary when other sync replicas are down and you want to | ||
| manually perform a failover. |
There was a problem hiding this comment.
Suggested change
| By the default the value is true which means that only sync replicas are candidates in the election. When the value is set to false, async replica is also considered but | |
| there is then an additional risk of experiencing a data loss. However, failovering to async replica may be necessary when other sync replicas are down and you want to | |
| manually perform a failover. | |
| By default, the value is `true`, which means that only sync replicas are candidates in the election. When the value is set to `false`, the async replica is also considered, but | |
| there is an additional risk of experiencing data loss. However, failover to an async replica may be necessary when other sync replicas are down and you want to | |
| manually perform a failover. |
There was a problem hiding this comment.
feel free to merge suggestions
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.
Release note
Document changes related to the user option of failovering only to the sync replica.
Related product PRs
PRs from product repo this doc page is related to:
memgraph/memgraph#2931
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documenting