[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106288#comment-14106288
]
Hongchao Deng commented on ZOOKEEPER-2016:
------------------------------------------
Another idea.
Regarding picking a backoff time in (min, max) interval, we should consider
using (min, max * factor) interval.
"factor" is affected by the number of clients.
Let's say I have 10 clients, I can use (0, 10ms). But if I have 100 clients,
(0, 100ms).
The default (min, max) is for *factor 1*.
How to define *factor 1* needs discussion.
How do you guys think?
> Automate client-side rebalancing
> --------------------------------
>
> Key: ZOOKEEPER-2016
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Hongchao Deng
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
