[
https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021207#comment-14021207
]
Bob Tiernay edited comment on STORM-213 at 6/8/14 3:30 PM:
-----------------------------------------------------------
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 already exists (from an
in-memory Kafka for example).
was (Author: btiernay):
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)
