[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017688#comment-13017688
 ] 

Vishal K commented on ZOOKEEPER-1044:
-------------------------------------

Hi Alex,

{quote}
The reconfiguration algorithm that I've started implementing assumes that new 
servers joining the system are connected as non-voting followers - this allows 
them to receive operations during the reconfiguration as they are proposed, and 
then they can remain followers in the new configuration. Your proposal for 
reconfiguration also assumed that you need to collect a quorum of acks from M', 
which you can't do if members of M' are Observers in M.
{quote}
Even if we consider OBSERVERs in M', do we need to wait to get a ack from them? 
We can just wait for quorum of FOLLOWERs in M' to ack.

{quote}
AFAIK, in order to convert an observer to a follower the process would need to 
be terminated and a new follower process created. So this is not about leader 
election (the intention is not to run leader election at all, unless a failure 
occurs during reconfiguration).
{quote}
I am not clear why this is needed. Can you elaborate on this?
If a follower becomes a observer (or viceversa), it will notice that once the 
membership is changed. Then it can shutdown its Learner object and go back to 
the LOOKING state. It will then rejoin the cluster as either FOLLOWER/OBSERVER.

I still think that with small changes to 107 we can achieve this feature as 
well.

-Vishal

> 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

Reply via email to