[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135962#comment-14135962
]
Hongchao Deng commented on ZOOKEEPER-2016:
------------------------------------------
I have finished a basic patch that does reconfig balance. This patch doesn't
contain anything regarding the Policy yet.
It would be great if you can summarize what we need for it.
My understanding for what to include in Policy:
1. (min,max) wait time
Client-side backoff is great. But I also realize in
[ClientCnxn|https://github.com/fengjingchao/zookeeper/blob/trunk/src/java/main/org/apache/zookeeper/ClientCnxn.java#L1063]
by default it has (0, 1000ms) backoff time. Should we consider how this can
affect our design here?
2. (before, after) updateServerList callback
what is the use case of these?
> Automate client-side rebalancing
> --------------------------------
>
> Key: ZOOKEEPER-2016
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Hongchao Deng
> Assignee: Hongchao Deng
> Attachments: ZOOKEEPER-2016.patch, draft-2.patch, draft-3.patch,
> draft.patch
>
>
> ZOOKEEPER-1355 introduced client-side rebalancing, which is implemented in
> both the C and Java client libraries. However, it requires the client to
> detect a configuration change and call updateServerList with the new
> connection string (see reconfig manual). It may be better if the client just
> indicates that he is interested in this feature when creating a ZK handle and
> we'll detect configuration changes and invoke updateServerList for him
> underneath the hood.
> Reviewboard: https://reviews.apache.org/r/25599/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
