Try to connect to any zookeeper, even if first one is dead/unavailable #824
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
proggga
force-pushed
the
fix_if_any_zookeeper_is_not_available
branch
5 times, most recently
from
f937e20 to
eb8de23
Compare
proggga
force-pushed
the
fix_if_any_zookeeper_is_not_available
branch
from
eb8de23 to
bfbcb59
Compare
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.
So I've seen a bug when first node of zookeeper cluster disabled/dead/has no dns - burrow dies. This is not a working solution, but this is workaround to go in cycle to find any valid broker from this list and the only fail