Fix v5.0 regression that left zoo pods unreachable #231
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.
The destabilization effort with v5.0.0 is going great :)
I didn't notice this flaw until I experimented with scaling for #228 (comment). The label change in #191 should have been reflected in the
zoo
service. It would have been apparent if I watched the logs during testing, with errors like:Maybe we should export prometheus metrics based on the
mntr
command, see https://zookeeper.apache.org/doc/r3.4.13/zookeeperAdmin.html#sc_zkCommands.