[
https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043164#comment-13043164
]
Vishal K commented on ZOOKEEPER-335:
------------------------------------
{quote}
note that step 5 has to occur soon after step 4 otherwise 55 will get a state
transfer rather than a diff and the problem will be fixed.
{quote}
Yes, I realized that. In our case, the new leader is sending diffs to the
faulty node.
{quote}
the fix isn't really performing a null transaction. (it is a work around, but
you also need to get the timing right.)
{quote}
It will be a workaround but it will be useful for pre zab 1.0 users. Why do you
think we need to get the timing right? We just need to ensure that the leader
performs the transaction before accepting any transactions from clients.
Do you agree that my workaround from the client side will work? (another
workaround is to always send SNAP instead of DIFF).
> 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
>
> Attachments: ZOOKEEPER-790.travis.log.bz2, faultynode-vishal.txt,
> zk.log.gz, zklogs.tar.gz
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira