[jira] Commented: (ZOOKEEPER-335) zookeeper servers should commit the new leader txn to their logs.

["Radu Marin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934189#action_12934189 ] 

Radu Marin commented on ZOOKEEPER-335:
--------------------------------------

We are hitting this problem often. A follower starts infinite looping on this, and it does not accept clients anymore.

It says LOOKING, than FOLLOWING, than "Leader epoch y is less than our epoch y +1 ", throws exception in shutdown and loops again.

The only way I could make it work again it was to cleanup the data directory and restart the server.

Any change this will be fixed soon ?


> 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: faultynode-vishal.txt, zk.log.gz, zklogs.tar.gz, ZOOKEEPER-790.travis.log.bz2
>
>
> 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.