You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 02:52:26 UTC

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

     [ https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-213:
-------------------------------
    Component/s: storm-core

> Decouple In-Process ZooKeeper from LocalCluster
> -----------------------------------------------
>
>                 Key: STORM-213
>                 URL: https://issues.apache.org/jira/browse/STORM-213
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            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)