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

runzhiwang updated LIVY-732:
----------------------------
    Description: 
Currently, the utilities of zookeeper mixed with ZooKeeperStateStore. To use 
the utility of zookeeper, the instance of ZooKeeperStateStore has to be created 
, which looks weird.

This Jira aims to achieve two targets:

1.  Extract the utilities of zookeeper from ZooKeeperStateStore to support such 
as distributed lock, service discovery and so on.

2.  ZooKeeperManager which contains the utilities of zookeeper should be a 
single instance.

  was:
Currently, the utilities of zookeeper mixed with ZooKeeperStateStore. To use 
the utility of zookeeper, I have to create a ZooKeeperStateStore which looks 
weird.

This Jira aims to achieve two targets:

1.  Extract the utilities of zookeeper from ZooKeeperStateStore to support such 
as distributed lock, service discovery and so on.

2.  ZooKeeperManager which contains the utilities of zookeeper should be a 
single instance.


> A Common Zookeeper Wrapper Utility 
> -----------------------------------
>
>                 Key: LIVY-732
>                 URL: https://issues.apache.org/jira/browse/LIVY-732
>             Project: Livy
>          Issue Type: Sub-task
>            Reporter: Yiheng Wang
>            Priority: Major
>
> Currently, the utilities of zookeeper mixed with ZooKeeperStateStore. To use 
> the utility of zookeeper, the instance of ZooKeeperStateStore has to be 
> created , which looks weird.
> This Jira aims to achieve two targets:
> 1.  Extract the utilities of zookeeper from ZooKeeperStateStore to support 
> such as distributed lock, service discovery and so on.
> 2.  ZooKeeperManager which contains the utilities of zookeeper should be a 
> single instance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to