[ https://issues.apache.org/jira/browse/ZOOKEEPER-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000035#comment-14000035 ]
Alexander Shraer commented on ZOOKEEPER-1699: --------------------------------------------- +1 > Leader should timeout and give up leadership when losing quorum of last > proposed configuration > ---------------------------------------------------------------------------------------------- > > Key: ZOOKEEPER-1699 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1699 > Project: ZooKeeper > Issue Type: Bug > Components: server > Affects Versions: 3.5.0 > Reporter: Alexander Shraer > Assignee: Alexander Shraer > Priority: Blocker > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1699-draft.patch, ZOOKEEPER-1699-draft.patch, > ZOOKEEPER-1699-v1.patch, ZOOKEEPER-1699-v2.patch, ZOOKEEPER-1699-v3.patch, > ZOOKEEPER-1699-v4.patch, ZOOKEEPER-1699-v4.patch, ZOOKEEPER-1699-v5.patch, > ZOOKEEPER-1699.patch > > > A leader gives up leadership when losing a quorum of the current > configuration. > This doesn't take into account any proposed configuration. So, if > a reconfig operation is in progress and a quorum of the new configuration is > not > responsive, the leader will just get stuck waiting for it to ACK the reconfig > operation, and will never timeout. -- This message was sent by Atlassian JIRA (v6.2#6252)