Zookeeper recursive#119
Open
gfelbing wants to merge 4 commits intoairbnb:masterfrom
freiheit-com:zookeeper_recursive
Open
Zookeeper recursive#119gfelbing wants to merge 4 commits intoairbnb:masterfrom freiheit-com:zookeeper_recursive
gfelbing wants to merge 4 commits intoairbnb:masterfrom
freiheit-com:zookeeper_recursive
Conversation
Looking for nodes in a given path, creates "zookeeper"-watcher for each node. The configuration for the created subwatcher is generated by the "zookeeper_recursive"-config, the string '#[service]' will be replaced by the name of the node. For a example-configuration see "synapse_zookeeper_recursive.yaml"
…ldren, due to random behaviour of haproxy with non-disjoint acl criteria
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.
This branch adds a new service watcher "zookeeper_recursive".
It doesn't generate backends directly, but generates new "zookeeper"-watcher for each persistent node under the configured path (including the path itself).
The configuration of the "zookeeper"-watcher is based on the configuration of the "zookeeper_recursive"-watcher, the "#[service]" will be replaced by the node's path in zookeeper, the "/" are replaced by "_".
With this functionality you doesn't have to know which services are existing or will exist in the future.
For an example configuration see "config/synapse_zookeeper_recursive.yaml"