[
https://issues.apache.org/jira/browse/BOOKKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802602#comment-13802602
]
Rakesh R commented on BOOKKEEPER-628:
-------------------------------------
Thanks for the comments.
Here my idea was to unify the zk usage in bookie server operations, also in
client side operations through one registration interface. Presently the zk
apis usage are scattered in Bookie, Cookie. IMHO, this will be helpful to focus
at common place for any ZK related logics like - ZK session handling, ZK acls.
bq.Why does ClientRegistrationManager have a createBookieInstance call?
Yeah, this should be at server side, which will be used by bookie format logic.
> 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-2.patch,
> BOOKKEEPER-628-interface-version.patch
>
>
> The idea is to improve/generalize the bookie registration process
--
This message was sent by Atlassian JIRA
(v6.1#6144)
