[
https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691577#comment-13691577
]
Rakesh R commented on BOOKKEEPER-628:
-------------------------------------
Thanks [~hustlmsp], [[email protected]] for the reviews.
I've separated out the client/server interfaces and if agrees, I'll integrate
this to our code base.
bq.zookeeper session expire handling
Presently ZooKeeperWatcherBase callback is doing the Expiry handling. I'm
thinking to move the zookeeper instantiation to the RegistrationManager#init()
method, and returns zk object. In bkclient, if user doesn't pass zk object will
do the zk instantiation and returns the object? How does it sound?
> Improve bookie registration interface
> -------------------------------------
>
> Key: BOOKKEEPER-628
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-628
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-628-interface-version-1.patch,
> BOOKKEEPER-628-interface-version.patch
>
>
> The idea is to improve/generalize the bookie registration process
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
