[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110078#comment-14110078
]
Alexander Shraer commented on ZOOKEEPER-2016:
---------------------------------------------
But only one of the clients invokes reconfig, so your solution will take care
of this guy, sure, but what happens with all the other clients ? what will
cause them to invoke updateServerList ?
To your question - the completion of reconfig is similar to the completion of
setData - the commit reached the server that responds to the client, and also
the leader of course since it sends the commit, but potentially no other server
(yet).
> Automate client-side rebalancing
> --------------------------------
>
> Key: ZOOKEEPER-2016
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2016
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Hongchao Deng
> Attachments: 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.2#6252)
