Patrick Hunt commented on ZOOKEEPER-107:

Submitted to me by a user. This describes a change both for servers and for 
clients. Currently servers 
share a configuration file that statically defines the cluster members 
(servers). Additionally clients are statically 
configured with a list of accessible servers.

"Instead of every client
maintaining a list of zookeeper servers, the servers should maintain
that info (e.g in a special 'node') and handle updates via the
server-to-server protcol. Then the client just needs to know the
server:port of *one* zookeeper server (or a bunch of 'forwarding
zookeepers' for redundancy) that it talks to and the servers take it
from there. 

If one server gets added to the collective, the server-to-server
protocol should propagate it among all servers and all servers update
their maps. Same if a zookeeper server gets moved out of rotation, there
should be an internal protocol to handle this and have all servers
update their maps. "

> Allow dynamic changes to server cluster membership
> --------------------------------------------------
>                 Key: ZOOKEEPER-107
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-107
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Patrick Hunt
> Currently cluster membership is statically defined, adding/removing hosts 
> to/from the server cluster dynamically needs to be supported.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to