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

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:09 UTC

[jira] [Updated] (ZOOKEEPER-1072) Support for embedded ZooKeeper

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

Michael Han updated ZOOKEEPER-1072:
-----------------------------------
    Fix Version/s:     (was: 3.5.3)
                   3.5.4

> Support for embedded ZooKeeper
> ------------------------------
>
>                 Key: ZOOKEEPER-1072
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1072
>             Project: ZooKeeper
>          Issue Type: Task
>          Components: server
>    Affects Versions: 3.3.0
>            Reporter: Vishal Kher
>              Labels: embedd, server
>             Fix For: 3.5.4, 3.6.0
>
>
> We have seen several cases where users have embedded zookeeper in
> their application instead of running ZooKeeper in an independent JVM.
> Different applications use different ways of starting and stopping QuorumPeer.
> Instead, we should provide a standard and simple API for starting/stopping
> zookeeper (and also document it).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)