[
https://issues.apache.org/jira/browse/HDFS-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054655#comment-14054655
]
Liang Xie commented on HDFS-6631:
---------------------------------
I could not repro on my dev box so far. probably it related with this code in
case "Thread.sleep(hedgedReadTimeoutMillis + 1);" ? if almost reach the
hedged read threshold (50ms), then a slow down,e.g. gc occur, or scheduler
related activity, so when this testing continues to run after 50+1 ms with cpu
begin to be scheduled again, then the counter can be 2.
It's just a guess, maybe a whole test log file will help us diagonise it.
Chris, do you still have that log outfile copy?
ps: if we enable the log level to ALL in this testing, i think it will very be
easier to understand all stuff:)
> TestPread#testHedgedReadLoopTooManyTimes fails intermittently.
> --------------------------------------------------------------
>
> Key: HDFS-6631
> URL: https://issues.apache.org/jira/browse/HDFS-6631
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, test
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Chris Nauroth
>
> {{TestPread#testHedgedReadLoopTooManyTimes}} fails intermittently. It looks
> like a race condition on counting the expected number of loop iterations. I
> can repro the test failure more consistently on Windows.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
