[
https://issues.apache.org/jira/browse/ZOOKEEPER-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Germán Blanco updated ZOOKEEPER-1732:
-------------------------------------
Attachment: ZOOKEEPER-1732-LOOSEN_RESTRICTIONS.patch
ZOOKEEPER-1732-LOOSEN_RESTRICTIONS.patch is the patch on the 3.4 branch
removing the check for the election round when joining an established ensemble.
It seems that the failure in FollowerResyncConcurrencyTest had nothing to do
with the change, and a lot to do with the fact that it was running in a virtual
environment that introduced a few delays in the execution.
This change passes all the tests and it allows my test of continous rolling
restarts to run without failures (at least 800 times, when it used to fail
before the 200th).
The patch also removes a couple of possibilities that made me uncomfortable,
namely:
- joining an ensemble that votes me as the leader.
- taking into account my own votes or votes that put me as a leader when
joining an ensemble.
"me" is the server joining the ensemble.
Since leader election is intrinsically unreliable, and odd things may happen, I
think it is better to avoid these just in case.
> 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,
> ZOOKEEPER-1732-LOOSEN_RESTRICTIONS.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 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
