[jira] [Commented] (ZOOKEEPER-1732) ZooKeeper server unable to join established ensemble

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

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

Flavio Junqueira commented on ZOOKEEPER-1732:
---------------------------------------------

I have downgraded this issue to major, it is a corner case and unlikely to happen often, but we still need to fix it. 

I'm thinking that we should update the peer epoch at the end of syncWithLeader rather than where it is in registerWithLeader. After syncing, we know the current epoch, so we should just update it there. I was also thinking that the we could update the zxid as well, although it doesn't matter too much.

The indentation is still wrong for me.

> ZooKeeper server unable to join established ensemble
> ----------------------------------------------------
>
>                 Key: ZOOKEEPER-1732
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1732
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: leaderElection
>    Affects Versions: 3.4.5
>         Environment: Windows 7, Java 1.7
>            Reporter: Germán Blanco
>            Assignee: Germán Blanco
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: CREATE_INCONSISTENCIES_patch.txt, zklog.tar.gz, ZOOKEEPER-1732-3.4.patch, ZOOKEEPER-1732-3.4.patch, ZOOKEEPER-1732.patch, ZOOKEEPER-1732.patch
>
>
> I have a test in which I do a rolling restart of three ZooKeeper servers and it was failing from time to time.
> I ran the tests in a loop until the failure came out and it seems that at some point one of the servers is unable to join the enssemble formed by the other two.



--
This message was sent by Atlassian JIRA
(v6.1#6144)