[
https://issues.apache.org/jira/browse/ZOOKEEPER-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143542#comment-13143542
]
Camille Fournier commented on ZOOKEEPER-1270:
---------------------------------------------
There's some extraneous stuff in ClientBase, but if anyone can repro this bug
locally and run it with this stack tracing on that would be useful.
> 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
