[
https://issues.apache.org/jira/browse/ZOOKEEPER-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747006#comment-14747006
]
Akihiro Suda commented on ZOOKEEPER-2080:
-----------------------------------------
We don't need to use {{java.nio.channels.SocketChannel}} (dicussed in
[ZOOKEEPER-2246|https://issues.apache.org/jira/browse/ZOOKEEPER-2246?focusedCommentId=14746992&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14746992]),
but seem to need redesign of QCM (ZOOKEEPER-901).
ZOOKEEPER-2164 seems also related.
So I link ZOOKEEPER-901 and ZOOKEEPER-2164 , and promote priority from Minor to
Major.
If this is inappropriate, please feel free to revert this change.
> ReconfigRecoveryTest fails intermittently
> -----------------------------------------
>
> Key: ZOOKEEPER-2080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Raul Gutierrez Segales
> Priority: Minor
> Attachments: jacoco-ZOOKEEPER-2080.unzip-grows-to-70MB.7z,
> repro-20150816.log
>
>
> I got the following test failure on MacBook with trunk code:
> {code}
> Testcase: testCurrentObserverIsParticipantInNewConfig took 93.628 sec
> FAILED
> waiting for server 2 being up
> junit.framework.AssertionFailedError: waiting for server 2 being up
> at
> org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529)
> at
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
