[ https://issues.apache.org/jira/browse/HDFS-11122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yiqun Lin updated HDFS-11122: ----------------------------- Attachment: HDFS-11122.003.patch I think the line {{miniCluster.corruptBlockOnDataNodes(block)} can assure the data to be corrupted, but it can't trigger the reported the bad blocks as onec. As [~tasanuma0829] suggested, we can read this file and assure the {{ClientProtocol#reportBadBlocks}} to be called. > TestDFSAdmin.testReportCommand fails due to timed out > ----------------------------------------------------- > > Key: HDFS-11122 > URL: https://issues.apache.org/jira/browse/HDFS-11122 > Project: Hadoop HDFS > Issue Type: Sub-task > Affects Versions: 3.0.0-alpha1 > Reporter: Yiqun Lin > Assignee: Yiqun Lin > Priority: Minor > Attachments: HDFS-11122.001.patch, HDFS-11122.002.patch, > HDFS-11122.003.patch > > > After HDFS-11083, the test {{TestDFSAdmi}} fails sometimes dueto timed out. > The stack > infos(https://builds.apache.org/job/PreCommit-HDFS-Build/17484/testReport/): > {code} > java.lang.Exception: test timed out after 30000 milliseconds > at java.lang.Thread.sleep(Native Method) > at > org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:268) > at > org.apache.hadoop.hdfs.tools.TestDFSAdmin.testReportCommand(TestDFSAdmin.java:540) > {code} > The timed out is happened in {{GenericTestUtils.waitFor}}. We can make a > improvement in the logic of waiting the corrupt blocks. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org