[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136316#comment-14136316
]
Alexander Shraer commented on ZOOKEEPER-2016:
---------------------------------------------
do we need both (1) and (2) ? if you allow users to provide a callback they can
probably implement the backoff easily themselves. You could of course also
provide a default implementation of the policy with min and max parameters.
I don't remember why we needed the "after" callback. I remember some discussion
about it but can't find it now.
> 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)
