WIP - Failure detection always finds first evicted server in array#4
Draft
WIP - Failure detection always finds first evicted server in array#4
Conversation
* this is expected to find the most recently evicted server * the time resolution appears insufficient for subsecond?
… server instead of the first server in the list that's been evicted
bradshjg
changed the title
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
1 participant
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.
Currently, the behavior of failure detection is to find the first server in the list that's evicted. When multiple servers have been evicted this means it's currently unclear which server was most recently evicted.
I'm not sure if there's a better way to gain insight into eviction behavior, but there are problems with this as well: