[
https://issues.apache.org/jira/browse/ZOOKEEPER-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Camille Fournier resolved ZOOKEEPER-1291.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 3.5.0
Release Note: Revision 1198053
> AcceptedEpoch not updated at leader before it proposes the epoch to followers
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1291
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1291
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: server
> Affects Versions: 3.4.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.4.0, 3.5.0
>
>
> It is possible that a leader proposes an epoch e and a follower adopts it by
> setting acceptedEpoch to e but the leader itself hasn't yet done so.
> While I'm not sure this contradicts Zab (there is no description of where the
> leader actually sets its acceptedEpoch), it is very counter intuitive.
> The fix is to set acceptedEpoch in getEpochToPropose, i.e., before anyone
> LearnerHandler passes the getEpochToPropose barrier.
> The fix is done as part of ZK-1264
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
