[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075314#comment-14075314
]
ASF GitHub Bot commented on STORM-213:
--------------------------------------
GitHub user wurstmeister opened a pull request:
https://github.com/apache/incubator-storm/pull/207
STORM-213: fixed NullPointerException
fixed NPE when submitting a topology to a LocalCluster with a decoupled ZK
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wurstmeister/incubator-storm STORM-213
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/207.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 #207
----
commit 839120514c4bfc9e2694ed44f32aa42a9f0d94bc
Author: wurstmeister <[email protected]>
Date: 2014-07-26T09:31:17Z
STORM-213: fixed NullPointerException
* that was caused by submitting a topology to a LocalCluster with a
decoupled ZK
----
> 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)
