Skip to content

Conversation

@gfelbing
Copy link

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"

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant