[
https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-335:
------------------------------------
Fix Version/s: (was: 3.2.0)
3.3.0
to fix this issue we require server -server protocol change. Thsi protocol
change will break backwards compatibility. To maintain backwards compatibility
the code becomes quite complex and tricky. Instead of making a last minute
change and having to do al lthe testing to check if backwards compatibily for
servers is maintained, I am moving it to 3.3 to see if we want to fix it in a
backwards compatible manner or fix it in 4.0 and break backwards compatibility.
> 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
> Fix For: 3.3.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.
