Ringpop: filter out unhealthy nodes #4764
Merged
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
vytautas-karpavicius
approved these changes
Mar 7, 2022
mantas-sidlauskas
added a commit
that referenced
this pull request
Mar 7, 2022
Pull Request Test Coverage Report for Build caf3336a-08f8-4dee-b27e-b21dc174595e
💛 - Coveralls |
mantas-sidlauskas
added a commit
that referenced
this pull request
Mar 21, 2022
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.
What changed?
Ringpop provider will not include unhealthy ring nodes
Why?
As ringpop keeps information about past members, it is needed to check node health status before node can be included to the ring
How did you test it?
Potential risks
Release notes
Documentation Changes