[
https://issues.apache.org/jira/browse/ZOOKEEPER-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880202#action_12880202
]
Flavio Paiva Junqueira commented on ZOOKEEPER-335:
--------------------------------------------------
Mike, There is one thing I don't understand. From the logs, it looks like
servers 1 and 3 are proposing a zxid of 0 (second field of notification) during
election, which makes me think that they had no state at all:
{noformat}
2010-06-17 14:35:40,714 - INFO
[QuorumPeer:/0:0:0:0:0:0:0:0:2181:fastleaderelect...@689] - Notification: 2,
8589934884, 2, 2, LOOKING, LOOKING, 2
2010-06-17 14:35:40,714 - INFO
[QuorumPeer:/0:0:0:0:0:0:0:0:2181:fastleaderelect...@799] - Notification: 3, 0,
1, 2, LOOKING, FOLLOWING, 1
2010-06-17 14:35:40,714 - INFO
[QuorumPeer:/0:0:0:0:0:0:0:0:2181:fastleaderelect...@799] - Notification: 3, 0,
1, 2, LOOKING, LEADING, 3
{noformat}
Server 2 on the other hand had accepted updates based on the zxid it proposes.
Were they supposed to have no state at all? Have you deleted your logs and
snapshots before restarting the servers?
> 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: zk.log.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.
-
You can reply to this email to add a comment to the issue online.
