[
https://issues.apache.org/jira/browse/ZOOKEEPER-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491409#comment-16491409
]
Patrick Hunt commented on ZOOKEEPER-3046:
-----------------------------------------
I checked job 37 above log artifacts and I don't see any "fsync" issues are you
would typically expect if the disk is slow.
{noformat}
if (syncElapsedMS > fsyncWarningThresholdMS) {
LOG.warn("fsync-ing the write ahead log in "
+ Thread.currentThread().getName()
+ " took " + syncElapsedMS
+ "ms which will adversely effect operation
latency. "
+ "File size is " + channel.size() + " bytes. "
+ "See the ZooKeeper troubleshooting guide");
}
{noformat}
Do you see it in any of the failures you're looking at?
Perhaps we should turn on GC logging and include that in the artifact?
> testManyChildWatchersAutoReset is flaky
> ---------------------------------------
>
> Key: ZOOKEEPER-3046
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3046
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.3, 3.4.12
> Reporter: Bogdan Kanivets
> Assignee: Bogdan Kanivets
> Priority: Minor
> Labels: flaky, pull-request-available
> Fix For: 3.6.0, 3.4.13, 3.5.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> According to the
> [dashboard|https://builds.apache.org/job/ZooKeeper-Find-Flaky-Tests/lastSuccessfulBuild/artifact/report.html]
> Â testManyChildWatchersAutoReset is flaky in 3.4 and 3.5
> [ZooKeeper_branch34_java10|https://builds.apache.org/job/ZooKeeper_branch34_java10//13]
> [ZooKeeper_branch35_java9|https://builds.apache.org/job/ZooKeeper_branch35_java9/253]
> Test times out and because of that ant doesn't capture any output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
