[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101232#comment-14101232
]
ASF GitHub Bot commented on STORM-213:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/207#issuecomment-52551092
@harshach could you take a quick look at this pull request? You did the
original decoupling.
@wurstmeister I'm not sure we have a policy on a change that needs a fix,
but has not been released yet. I reopened STORM-213, we can close it again
when the NPE is merged in. We may change this in the future though.
> 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)
