zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishal K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-335) zookeeper servers should commit the new leader txn to their logs.
Date Tue, 07 Jun 2011 13:17:58 GMT

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

Vishal K commented on ZOOKEEPER-335:

Hi Ben, Flavio,

Thanks. We will try out the patch.

For the record, after some more discussion with Ben I realized that none of the workarounds
that I was trying would work. Fixing this bug would need change in the protocol. Thanks for
the clarification..

> 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-335.patch, ZOOKEEPER-335_2.patch, 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

View raw message