[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131098#comment-14131098
]
Hongchao Deng commented on ZOOKEEPER-2016:
------------------------------------------
Hi [~shralex].
I think
{code}
zk.updateServerList(connectString);
{code}
only closes current client connect if it need to drop.
However, in my test, I want to have explicit point after which all clients have
finished rebalance. Do you know any way to achieve it? I wonder if we can make
ZooKeeper::updateServerList return only after the client has reconnected. Let
me know your thoughts. Thanks!
> 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: draft-2.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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
