[
https://issues.apache.org/jira/browse/HDFS-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452173#comment-13452173
]
Eli Collins commented on HDFS-3910:
-----------------------------------
With this patch reproducing HDFS-3902 now yields a test failure with an
explicit error message:
{noformat}
Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 92.861 sec <<<
FAILURE!
testBlockCorruptionPolicy(org.apache.hadoop.hdfs.TestDatanodeBlockScanner)
Time elapsed: 28.169 sec <<< ERROR!
java.util.concurrent.TimeoutException: Timed out waiting for
/tmp/testBlockVerification/file1 to reach 3 replicas
at
org.apache.hadoop.hdfs.DFSTestUtil.waitReplication(DFSTestUtil.java:534)
at
org.apache.hadoop.hdfs.TestDatanodeBlockScanner.testBlockCorruptionPolicy(TestDatanodeBlockScanner.java:219)
{noformat}
> DFSTestUtil#waitReplication should timeout
> ------------------------------------------
>
> Key: HDFS-3910
> URL: https://issues.apache.org/jira/browse/HDFS-3910
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: test
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-3910.txt
>
>
> DFSTestUtil#waitReplication never times out so test execution fails only when
> the mvn test executor times out. This leaves a stray test process around, an
> example is HDFS-3902. Let's make waitReplication do something like bail after
> it has checked block locations 10 times for one file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
