[
https://issues.apache.org/jira/browse/ZOOKEEPER-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143602#comment-13143602
]
Camille Fournier commented on ZOOKEEPER-1270:
---------------------------------------------
It seems to me that everything comes up ok, and starts the election process,
elects a leader, and gets a snapshot from the leader. But in the logs where you
have 2 followers very closely synched in time (never my local box but seems to
happen on the build boxes occasionally), after the followers have claimed to
write a snapshot to disk (which means they must have gotten the NEWLEADER
message) the whole process then stops, and you see no logs from the leader
indicating it ran processAck for either follower. It feels to me like it could
be a race condition in the leader somewhere, causing it to somehow miss that
ACK but I can't seem to find it. Nothing in the diffs from the checkin related
to ZAB1.0 seem to be much of a culprit... I'm a bit stumped but going to keep
looking.
> 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
>
>
> 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
