[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026836#comment-14026836
]
ASF GitHub Bot commented on STORM-213:
--------------------------------------
GitHub user harshach opened a pull request:
https://github.com/apache/incubator-storm/pull/137
STORM-213. Decouple In-Process ZooKeeper from LocalCluster.
Added a constructor to LocalCluster to pass in zookeeper host and port.
Users can call LocalCluster with external zookeeper
(let [cluster (LocalCluster. "localhost" 2181)]
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-213-V2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/137.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #137
----
commit aabf49c2e2929a20847dbe54741acfa1132224a1
Author: Sriharsha Chintalapani <[email protected]>
Date: 2014-06-10T18:41:11Z
STORM-213. Decouple In-Process ZooKeeper from LocalCluster.
----
> 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
> Labels: LocalCluster, ZooKeeper
>
> 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)
