[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043588#comment-16043588
 ] 

Hadoop QA commented on ZOOKEEPER-2803:
--------------------------------------

-1 overall.  GitHub Pull Request  Build
      

    +1 @author.  The patch does not contain any @author tags.

    +0 tests included.  The patch appears to be a documentation patch that 
doesn't require tests.

    -1 javadoc.  The javadoc tool appears to have generated 1 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    -1 findbugs.  The patch appears to introduce 48 new Findbugs (version 
3.0.1) warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/781//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/781//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/781//console

This message is automatically generated.

> Flaky test: org.apache.zookeeper.test.CnxManagerTest.testWorkerThreads
> ----------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2803
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2803
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.10
>            Reporter: Abraham Fine
>            Assignee: Abraham Fine
>
> We have noticed on internal executions of the integration tests rare failures 
> of org.apache.zookeeper.test.CnxManagerTest.testWorkerThreads.
> {code}
> java.lang.RuntimeException: Unable to run quorum server 
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:565)
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:520)
>       at 
> org.apache.zookeeper.test.CnxManagerTest.testWorkerThreads(CnxManagerTest.java:328)
>       at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> Caused by: java.io.IOException: The current epoch, 0, is older than the last 
> zxid, 4294967296
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:546)
> {code}
> along with this strange stack trace in the logs:
> {code}
> java.nio.channels.ClosedByInterruptException
>       at 
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
>       at sun.nio.ch.FileChannelImpl.force(FileChannelImpl.java:380)
>       at 
> org.apache.zookeeper.common.AtomicFileOutputStream.close(AtomicFileOutputStream.java:71)
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.writeLongToFile(QuorumPeer.java:1232)
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.setCurrentEpoch(QuorumPeer.java:1253)
>       at 
> org.apache.zookeeper.server.quorum.Learner.syncWithLeader(Learner.java:412)
>       at 
> org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:83)
>       at 
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:851)
> {code}
> It appears that this failure is related to the usage of {{((FileOutputStream) 
> out).getChannel().force(true)}} in {{AtomicFileOutputStream}}. 
> {{FileChannel#force}} appears to be interruptible, which is not desirable 
> behavior when writing the epoch file. The interrupt may be triggered by the 
> repeated starting and shutting down of quorum peers in {{testWorkerThreads}}. 
> Branch 3.5 uses {{FileDescriptor#sync}} which is not interruptible and does 
> not appear to have the same problem.
> I was able to find another JIRA ticket describing a similar issue here: 
> https://issues.apache.org/jira/browse/DERBY-4963
> There is also interesting discussion in ZOOKEEPER-1835 (where the change was 
> made for 3.5) although these discussions appear to be Windows centric (we 
> noticed the issue on Linux) 
> https://issues.apache.org/jira/browse/ZOOKEEPER-1835 
> The failure appears to have popped up on "ZOOKEEPER-2297 PreCommit Build 
> #3241" but jenkins cleared out the logs (I only still have the test report 
> from the mailing list).
> In addition, {{testWorkerThreads}} appears to be failing every few months on 
> Solaris on Apache Jenkins (for 3.4 ZooKeeper_branch34_solaris - Build # 1430  
> and 3.5 ZooKeeper_branch35_solaris - Build # 387), but at the time I wrote 
> this Jenkins had cleaned out the logs from the latest failed run so I have no 
> way of determining if the cause is the same.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to