[
https://issues.apache.org/jira/browse/HDFS-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051293#comment-14051293
]
Liang Xie commented on HDFS-6614:
---------------------------------
bq. I did discover that the new testHedgedReadLoopTooManyTimes test is failing
on my Windows VM on the assertion for the loop count
Did your Windows VM run on a SSD or similar fast storage ?
I think there's possibility that if "the second read + the second creating
block reader" took less then 1ms, then our asserted loopTimeNum could be 2, not
3. Anyway, i assume changing "assertEquals(3,
input.getHedgedReadOpsLoopNumForTesting());" with
"assertTrue(input.getHedgedReadOpsLoopNumForTesting() <=3 &&
input.getHedgedReadOpsLoopNumForTesting() >=2);", should be better.
> shorten TestPread run time with a smaller retry timeout setting
> ---------------------------------------------------------------
>
> Key: HDFS-6614
> URL: https://issues.apache.org/jira/browse/HDFS-6614
> Project: Hadoop HDFS
> Issue Type: Test
> Components: test
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
> Attachments: HDFS-6614.txt
>
>
> Just notice logs like this from TestPread:
> DFS chooseDataNode: got # 3 IOException, will wait for 9909.622860072854 msec
> so i tried to set a smaller retry window value.
> Before patch:
> T E S T S
> -------------------------------------------------------
> Running org.apache.hadoop.hdfs.TestPread
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 154.812 sec -
> in org.apache.hadoop.hdfs.TestPread
> After the change:
> T E S T S
> -------------------------------------------------------
> Running org.apache.hadoop.hdfs.TestPread
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 131.724 sec -
> in org.apache.hadoop.hdfs.TestPread
--
This message was sent by Atlassian JIRA
(v6.2#6252)
