[
https://issues.apache.org/jira/browse/ZOOKEEPER-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111751#comment-14111751
]
Hongchao Deng commented on ZOOKEEPER-2016:
------------------------------------------
[~shralex]
I attached another draft.
Basic ideas:
1. an executor watching the znode on getConfig()
2. it would be notified on reconfig change and rebalance upon that. A special
case is on first connect, which could happen on fresh or reconnect after
session expired, it will also update the list. It could be turned off
nonetheless.
Is this what you are expecting? Let's use this as base for more discussion.
> 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.2#6252)
