[
https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879548#action_12879548
]
Patrick Hunt commented on ZOOKEEPER-335:
----------------------------------------
We are unable to reproduce this issue. If you can provide the server logs (all
servers) and attach them to this jira it would be very helpful. Some detail on
the approx time of the issue so we can correlate to the logs would help too
(summary of what you did/do to cause it, etc... anything that might help us
nail this one down).
Detail on ZK version, OS, Java version, HW info, etc... would also be of use to
us.
> 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.
