fix(autocluster): avoid stopping autocluster too eagerly #242
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
Specifically when discovery found no nodes. This can happen due to a lot of various race conditions in real-world systems, e.g.: DNS information propagating with some delay. Now the assumption is that discovery should find at least a single node. With singleton clusters, this will be the current node most of time.
terry-xiaoyu
approved these changes
Dec 20, 2024
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.
Specifically when discovery found no nodes. This can happen due to a lot of various race conditions in real-world systems, e.g. DNS information propagating with some delay.
Now the assumption is that discovery should find at least a single node. With singleton clusters, this will be the current node most of time anyway.