Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Wed, 5 Apr 2017 00:04:41 +0000 (UTC)
From: "Michael Han (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13061574.1491349164000.206371.1491350681676@Atlassian.JIRA>
In-Reply-To: <JIRA.13061574.1491349164000@Atlassian.JIRA>
References: <JIRA.13061574.1491349164000@Atlassian.JIRA> <JIRA.13061574.1491349164132@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-2746) Leader hand-off during dynamic
 reconfig is best effort, while test always expects it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 05 Apr 2017 00:04:46 -0000


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

Michael Han commented on ZOOKEEPER-2746:
----------------------------------------

merged to master https://github.com/apache/zookeeper/commit/d061f1b5a5eca108e566a68e6f7aa07913c90ac3

> Leader hand-off during dynamic reconfig is best effort, while test always expects it
> ------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2746
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2746
>             Project: ZooKeeper
>          Issue Type: Test
>    Affects Versions: 3.5.2
>            Reporter: Michael Han
>            Assignee: Michael Han
>             Fix For: 3.6.0
>
>
> When non-trivial config change happens on the leader (e.g. port change, role change) to minimize disruption of quorum we do leader hand off by having the current leader nominate the next leader instead of kicking off a full leader election.
> However this is a best effort and not a guarantee that the new leader of the quorum will be the nominated leader: it is possible that the nominated leader fail to establish the leadership during sync phase, which leads to new election rounds and a different leader elected. 
> In ReconfigTest.testPortChange one check is the new leader after dynamic reconfig of the current leader has to be a different leader; based on what described earlier this is not always the case as the nominated leader might fail to get a quorum to ack its leadership during sync phase, and the old leader might end up as the new leader. We could either fixed the test by removing the check, or always guarantee that the new leader after dynamic reconfig is the nominated leader (which does not make much sense given the nominated leader also has a possibility to crash.).


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)