Github user atdixon commented on the pull request:
https://github.com/apache/storm/pull/432#issuecomment-74537246
Zookeeper and its clients require static list of hosts in its configuration
[1]. Exhibitor (in addition to supervision, backup, etc.) can provide the
Zookeeper server list to Curator clients (via Curator's Exhibitor support [2]),
so that the client can dynamically update its Zookeeper servers list.
This provides a more robust connection to our Zookeeper ensemble from Storm
(supporting zookeeper cluster scale-up/down, whole node replacements, rolling
upgrades, outages, etc. all w/o restarting Storm.) It also allows Storm to
discover our Zookeeper cluster through curator-exhibitor instead of requiring
the full Zookeeper ensemble to be hard-listed into the Storm configuration.
With this patch, you can (optionally) provide Exhibitor servers *in place
of* Zookeeper servers in the storm config and Storm will discover your
Zookeeper ensemble. This is why it should go into storm.yaml.
[1]
http://zookeeper.apache.org/doc/r3.5.0-alpha/zookeeperProgrammers.html#ch_gotchas
[2] http://curator.apache.org/exhibitor.html
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
