[
https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018368#comment-13018368
]
Vishal K commented on ZOOKEEPER-1044:
-------------------------------------
Hi Alex,
Agreed. Thats why I suggested that in the reconfig algorithm leader(M) should
wait to receive ack from a quorum of followers in M' (instead of just quorum of
M'). The same way leader(M) waits to receive ack from followers in M. So it is
a small change in the algorithm. What do you think?
Any feedback on my earlier comment regarding restarting the process and
difficulty of implementation?
Thanks.
> Allow dynamic changes to roles of a peer
> ----------------------------------------
>
> Key: ZOOKEEPER-1044
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1044
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: quorum
> Affects Versions: 3.3.0
> Reporter: Vishal K
> Fix For: 3.4.0
>
>
> Requirement: functionality that will reconfigure
> a OBSERVER to become a voting member and vice versa.
> Example of usage:
> 1. Maintain the Quorum size without changing the cluster size - in a 5
> node cluster with 2 observers, I decide to decommission a voting
> member. Then, I would like to configure one of my observers to be a
> follower without any down time.
> 2. Added a new server to the cluster that has better resources than
> one of the voting peers. Make the new node as voting peer and the old
> one as observer.
> 3. Reduce the size of voting member for performance reasons.
> Fix to ZOOKEEPER-107 might automatically give us this functionality.
> It will be good to confirm that, and if needed, highlight work
> that might be needed in addition to ZOOKEEPER-107.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira