You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Bob Tiernay (JIRA)" <ji...@apache.org> on 2014/06/08 17:32:02 UTC

[jira] [Commented] (STORM-213) Decouple In-Process ZooKeeper from LocalCluster

    [ https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021207#comment-14021207 ] 

Bob Tiernay commented on STORM-213:
-----------------------------------

Agreed, this would be a very useful feature for integration testing. Right now disabling {{LocalCluster}}'s in-memory ZooKeeper would be great since it really slows down startup time when another ZK instance exists (form in-memory Kafka for example).

> 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)