[
https://issues.apache.org/jira/browse/ZOOKEEPER-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-1270:
------------------------------------
Fix Version/s: (was: 3.4.0)
3.4.1
It looks like this issue might be related to Read only mode - after applying
the patch from ZOOKEEPER-1268 I could not get this to happen again. I ran the
QuorumPeerMain test over 30 times without a single failure, I run the full test
suite 3 times without any issues. It's looking like ROM is somehow causing this
failure - which seems likely given the logs and the way ROM operates.
I'm moving this out of 3.4.0 now that ZOOKEEPER-1268 is applied there and I can
no longer reproduce.
> 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.5.0, 3.4.1
>
> Attachments: testEarlyLeaderAbandonment.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
