[
https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201343#comment-14201343
]
Jian Fang commented on ZOOKEEPER-1044:
--------------------------------------
BTW, I wonder if it is possible for zookeeper to manage the role change by
itself in the future. For example, I can specify that I only expect 5
participants in normal operations. The zookeeper peers can make an election on
which peers should be participants and which should be observers by themselves.
Also do the election once participants are lost. In this way, I can simply
start up 8 zookeeper instances, for instance. And I don't need any management
tool or code to babysit the zookeeper quorum. I think this should dramatically
reduce the operational overhead especially when people run zookeeper in cloud
because a cloud instance could be gone forever and at any time.
> 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)
