[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159215#comment-14159215
]
ASF GitHub Bot commented on STORM-213:
--------------------------------------
Github user wurstmeister commented on the pull request:
https://github.com/apache/storm/pull/207#issuecomment-57912008
As far as I can tell this is just a static environment dump and does not
mean that we start a new zookeeper server, see ([ZooKeeperServer]
(https://svn.apache.org/repos/asf/zookeeper/tags/release-3.4.5/src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java))
```
static {
LOG = LoggerFactory.getLogger(ZooKeeperServer.class);
Environment.logEnv("Server environment:", LOG);
}
```
> Decouple In-Process ZooKeeper from LocalCluster
> -----------------------------------------------
>
> Key: STORM-213
> URL: https://issues.apache.org/jira/browse/STORM-213
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Sharmarke Aden
> Assignee: Sriharsha Chintalapani
> Labels: LocalCluster, ZooKeeper
> Fix For: 0.9.3
>
>
> 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.3.4#6332)
