[
https://issues.apache.org/jira/browse/ZOOKEEPER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722368#action_12722368
]
Henry Robinson commented on ZOOKEEPER-107:
------------------------------------------
I think the issue of how to locate an ensemble whose makeup has changed needs
to be discussed separately. I've got an idea for how I'd suggest doing it, but
will leave that until I've got the view change stuff working. Once a new leader
has been elected, it will need to publish this somewhere (probably both
internal to ZK in /zookeeper/ensemble and externally). Observers can use one of
those routes to find the leader.
At the moment, Observers are just followers that a) can't make most mutable
proposals b) don't get either PROPOSE or COMMIT messages, just INFORM ones with
the payload and c) can propose view changes, not necessarily to include
themselves. So an Observer attaches to a leader, syncs and maybe listens in on
the proposal stream for a while and then upgrades itself by issuing a view
change request.
> 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
> Assignee: Henry Robinson
> 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.
