[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Germán Blanco updated ZOOKEEPER-1732:
-------------------------------------
Attachment: test_loosen_restrictions.tar.gz
The file test_loosen_restrictions.tar.gz contains a patch to loosen the
checking of election epoch when a new server joins an established ensemble.
Also contains the report of the test case that failed when running the
regression on branch-3.4 using this patch.
Test case is FollowerResyncConcurrencyTest, I can't tell the relationship
between the failure and the change. I guess there are more things to think
about, but maybe this points to some problem already.
I also started the long test with all the rolling restarts, so far it is going
ok.
> 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
> Priority: Blocker
> Fix For: 3.5.0, 3.4.6
>
> Attachments: test_loosen_restrictions.tar.gz, zklog.tar.gz
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
