[jira] [Commented] (HDFS-9583) TestBlockReplacement#testDeletedBlockWhenAddBlockIsInEdit occasionally fails

["Lin Yiqun (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227625#comment-15227625 ] 

Lin Yiqun commented on HDFS-9583:
---------------------------------

Hi, [~jojochuang], this issue has fixed in HDFS-9865, can we duplicate to that.

> TestBlockReplacement#testDeletedBlockWhenAddBlockIsInEdit occasionally fails
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-9583
>                 URL: https://issues.apache.org/jira/browse/HDFS-9583
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>         Environment: Jenkins
>            Reporter: Wei-Chiu Chuang
>
> https://builds.apache.org/job/Hadoop-Hdfs-trunk/2647/testReport/junit/org.apache.hadoop.hdfs.server.datanode/TestBlockReplacement/testDeletedBlockWhenAddBlockIsInEdit/
> Looking at the code, the test expects that replacing a block from one data node to another  issues a delete request to FsDatasetAsyncDiskService.deleteAsync(), which should have print log "Scheduling ... file ... for deletion", and it waited for 3 seconds. However, it never occurred.
> I think the test needs a better way to determine if the delete request is executed, rather than using a fixed time out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)