Conversation
When trying to find if a candidate has already been selected, avoid choosing a node that is in WAIT_PRIMARY. As we don't change the state of such a node when it becomes unhealthy, that might lead to strange results when two failover situations happen one after another. Also guard demoted to cachingup transitions to only happen when the current primary is known healthy.
JelteF
approved these changes
May 6, 2021
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
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 trying to find if a candidate has already been selected, avoid choosing
a node that is in WAIT_PRIMARY. As we don't change the state of such a node
when it becomes unhealthy, that might lead to strange results when two
failover situations happen one after another.
Also guard demoted to cachingup transitions to only happen when the current
primary is known healthy.