[
https://issues.apache.org/jira/browse/ZOOKEEPER-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968526#comment-13968526
]
Flavio Junqueira commented on ZOOKEEPER-1699:
---------------------------------------------
Hi [~shralex],
It looks good. The use of Proposal seems to be convenient because of the
hasAllQuorums call, but it sounds a bit out of place. Could we use the quorum
verifier directly instead?
In the case we don't follow this suggestion, we should at least call it
something else other than dummyProposal, like syncedAckSet or something like
that.
> 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-v1.patch, ZOOKEEPER-1699-v2.patch,
> ZOOKEEPER-1699-v3.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)
