Benjamin Reed commented on ZOOKEEPER-107:

i think i agree with flavio about using setData instead of NEWVIEW. (to be 
honest we had talked about this approach a while back in private.) we have 
already reserved the /zookeeper namespace (by convention). so if we use 
/zookeeper/ensemble to store the ensembles, then we can just use setData and 
getData to implement NEWVIEW and GETVIEW. This has two nice properties: 1) we 
don't need to touch the protocol code at all. 2) we can use standard clients to 
administer the view changes. for example, you could use the cli to get and 
manipulate the views.

@raghu: here is the scenario for split brain: you have an ensemble of A, B, C, 
D, and E. Your new view will be made up of B, C, D, E, and F. if your update 
only hits D, E, and F, you can have two working ZooKeeper instances: A, B, C 
and D, E, F, thus giving your split brain.

> 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
>         Attachments: SimpleAddition.rtf
> 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