[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101813#comment-14101813
]
ASF GitHub Bot commented on STORM-213:
--------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/incubator-storm/pull/207#issuecomment-52587264
@revans2 @wurstmeister sorry about the bug. This change looks good to me I
tested it by running word_count topology with LocalCluster. +1
> Decouple In-Process ZooKeeper from LocalCluster
> -----------------------------------------------
>
> Key: STORM-213
> URL: https://issues.apache.org/jira/browse/STORM-213
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Reporter: Sharmarke Aden
> Assignee: Sriharsha Chintalapani
> Labels: LocalCluster, ZooKeeper
> Fix For: 0.9.3-incubating
>
>
> Currently there is no way to independently start ZooKeeper instance and have
> LocalCluster use this instance. It would be great if there was an option to
> tell LocalCluster to not start its own in-process ZooKeeper and instead rely
> on an already running In-Process instance.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
