[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120906#comment-14120906
]
Hongchao Deng commented on ZOOKEEPER-2016:
------------------------------------------
{quote}
to avoid the first connect issue you could do something like this:
if (version == -1)
{ version = configVersion; return; }
{quote}
What if a reconfig happened when a server crashed and restarted. If so, it
looks like "first connect" but client still uses the old list.
I wonder if it's safe to just do a updateServerList() because ZOOKEEPER-1355
says "there is no excessive/unnecessary client migration". If there is no
change/reconfig, would it be no difference to call updateServerList().
> 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-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)
