You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2017/02/14 21:27:41 UTC

[jira] [Commented] (BOOKKEEPER-1006) Remove Bookie global ZK Instance

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

Robert Joseph Evans commented on BOOKKEEPER-1006:
-------------------------------------------------

[~mmerli],

Could you assign this to [~govindmenon]?

> Remove Bookie global ZK Instance
> --------------------------------
>
>                 Key: BOOKKEEPER-1006
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1006
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>    Affects Versions: 4.5.0, 4.6.0
>            Reporter: Govind Menon
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Bookie has had a Zookeeper client for the whole process up to now. This
> is only ever used in garbage collection though. This change moves the
> creation and usage of the zookeeper client to the garbage collection
> thread. It now creates a new zookeeper client for each GC iteration, and
> tears it down afterwards. This means that if there is a problem with the
> zookeeper connection, it will only exist for one iteration of garbage
>  collection.
> This work was originally done by Ivan Kelly and I am just pushing it back to open source



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