[ZOOKEEPER-335] zookeeper servers should commit the new leader txn to their logs.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.4.0
• Component/s: server
• Hadoop Flags: Reviewed
• Assignee: Benjamin Reed
• Reporter: Mahadev Konar
• Created: 04/Mar/09 18:55
• Updated: 17/Nov/19 10:05
• Resolved: 14/Jun/11 05:14

Description

currently the zookeeper followers do not commit the new leader election. This will cause problems in a failure scenarios with a follower acking to the same leader txn id twice, which might be two different intermittent leaders and allowing them to propose two different txn's of the same zxid.

Issue Links

• breaks: ZOOKEEPER-1278 acceptedEpoch not handling zxid rollover in lower 32bits
• is related to: ZOOKEEPER-790 Last processed zxid set prematurely while establishing leadership
• relates to: ZOOKEEPER-3608 add a documentation about currentEpoch and acceptEpoch

Sub-Tasks

• modify leader/follower code to correctly deal with new leader: Closed
• modify leader election to correctly take into account current epoch: Closed