[ https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879520#action_12879520 ]
Vishal K commented on ZOOKEEPER-335: ------------------------------------ Hi, We are running into this bug very often (almost 60-75% hit rate) while testing our newly developed application over ZK. This is almost a blocker for us. Will the fix be simplified if backward compatibility was not an issue? Thanks. > zookeeper servers should commit the new leader txn to their logs. > ----------------------------------------------------------------- > > Key: ZOOKEEPER-335 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-335 > Project: Zookeeper > Issue Type: Bug > Components: server > Affects Versions: 3.1.0 > Reporter: Mahadev konar > Assignee: Mahadev konar > Priority: Blocker > Fix For: 3.4.0 > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.