etcd peer discovery fixes (backport #11439) #11445
Merged
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
Instead of relying on the complex and non-determinstic default node selection mechanism inside peer discovery this change makes the etcd backend implemention make the leader selection itself based on the etcd create_revision of each entry. Although not spelled out anywhere explicitly is likely that a property called "Create Revision" is going to remain consistent throughout the lifetime of the etcd key. Either way this is likely to be an improvement on the current approach. (cherry picked from commit 3390fc9)
As the primary mirror may sometimes fail there is now a fall back. (cherry picked from commit 5a94049)
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.
Instead of relying on the complex and non-determinstic default node
selection mechanism inside peer discovery this change makes the
etcd backend implemention make the leader selection itself based on
the etcd
create_revisionof each entry. Although not spelled out anywhereexplicitly is likely that a property called "Create Revision" is going
to remain consistent throughout the lifetime of the etcd key.
Either way this is likely to be an improvement on the current approach.
This is an automatic backport of pull request #11439 done by Mergify.