[
https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201106#comment-14201106
]
Jian Fang commented on ZOOKEEPER-1044:
--------------------------------------
Thanks Hongchao and Alexander for your quick response.
Alexander, I am still a bit confused while you said 5 servers can tolerate a
failure of 2 and 6 servers can tolerate only 2 failures. Do the 5 servers and 6
servers include observers as well? From documents, seems only participants are
involved in the voting, right? Do you mean 5 participants and 6 participants?
If that is true, do you suggest I set all 6 peers to be participants instead of
3 participants and 3 observers?
Also, let us consider we have 4 participants, do we have a scenario that 2
peers have the same vote, but different from the other two? Or this is not
possible because zookeeper always uses a leader?
Thanks again.
> 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 Kher
> Assignee: Alexander Shraer
> Fix For: 3.5.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 was sent by Atlassian JIRA
(v6.3.4#6332)
