[
https://issues.apache.org/jira/browse/ZOOKEEPER-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144208#comment-13144208
]
Patrick Hunt commented on ZOOKEEPER-1270:
-----------------------------------------
Ok, here's whats' happening wrt the test not failing.
Look after the time index I provided, notice that the followers fail to hear
from the leader, at which point they re-negotiate the quorum, at which point
the quorum IS RE-EST SUCCESSFULLY, and the clients are now able to connect to
the service and the test continues.
This is a side-effect of increasing the "waitForAll" time that we allow. We are
giving time for the quorum to re-establish itself after the "hang".
Likely this is why we have not seen this in the past, if it did every happen
(in any test) it might have been ignored due to recovery.
so now that we know the test is really failing, perhaps we should just go back
to 10 iterations/1sec sleep so that the test will actually fail. (or perhaps
there's a better way to address this in the test?)
> testEarlyLeaderAbandonment failing intermittently, quorum formed, no serving.
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1270
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1270
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Reporter: Patrick Hunt
> Priority: Blocker
> Fix For: 3.4.0, 3.5.0
>
> Attachments: ZOOKEEPER-1270tests.patch, ZOOKEEPER-1270tests2.patch,
> testEarlyLeaderAbandonment.txt.gz, testEarlyLeaderAbandonment2.txt.gz,
> testEarlyLeaderAbandonment3.txt.gz
>
>
> Looks pretty serious - quorum is formed but no clients can attach. Will
> attach logs momentarily.
> This test was introduced in the following commit (all three jira commit at
> once):
> ZOOKEEPER-335. zookeeper servers should commit the new leader txn to their
> logs.
> ZOOKEEPER-1081. modify leader/follower code to correctly deal with new leader
> ZOOKEEPER-1082. modify leader election to correctly take into account current
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
