[
https://issues.apache.org/jira/browse/STORM-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359840#comment-14359840
]
ASF GitHub Bot commented on STORM-702:
--------------------------------------
Github user atdixon commented on the pull request:
https://github.com/apache/storm/pull/432#issuecomment-78764060
The config is optional. If not present, everything works as usual.
On Thu, Mar 12, 2015 at 9:18 PM, Harsha <[email protected]> wrote:
> @atdixon @revans2 with this patch can a user who doesn't want use
exhibitor avoid it by not having the config or the user must have the config in
their storm.yaml.
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/apache/storm/pull/432#issuecomment-78750701
> Apache Exhibitor support
> ------------------------
>
> Key: STORM-702
> URL: https://issues.apache.org/jira/browse/STORM-702
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Aaron Dixon
> Priority: Critical
>
> Storm connects to Zookeeper via an explicit list of zookeeper hosts.
> Apache Exhibitor offers zookeeper cluster discovery and management features
> allowing for dynamically resizing zookeeper clusters, restarting and
> replacing zk machines in the cluster, etc.
> Curator supports creating zookeeper client connections using exhibitor hosts.
> Storm should allow (optionally) for connection to its Zookeeper clusters
> through Exhibitor.
> Here is the github pull request that prompted this ticket, and that
> introduces optional exhibitor configuration and exhibitor support in Storm:
> https://github.com/apache/storm/pull/432
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
