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

Xiaoqiao He commented on HDFS-14720:
------------------------------------

Thank [~surendrasingh] for your detailed information, this case is related to 
HDFS-10453, however I do not think it is serious issue. Anyway, it needs to fix.
1. HDFS-10453 try to avoid stuck NameNode due to a corner case which 
(ReplicationMonitor) replica one block who is deleted by another thread.
2. HDFS-10453 does not involve DataNode, then we meet this WARN log.
3. IIRC, initial patch for HDFS-10453 is just very same as 
[^HDFS-14720.001.patch], after long time discussion,  it becomes to the last 
patch.
Back to this JIRA, I agree we should ignore to replicate DELETED block and 
avoid send COPY command (for DELETED block) which is useless to DataNode. IIUC, 
even that, when receive invalid command, DataNode will leave one WARN log and 
ignore to transfer this block, later it will receive DELETE command at next 
heartbeat response then remove this block replica. Totally, it is not serious 
issue but one useless command. Anyway, it is better to avoid it. Please correct 
if something wrong.

> DataNode shouldn't report block as bad block if the block length is 
> Long.MAX_VALUE.
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-14720
>                 URL: https://issues.apache.org/jira/browse/HDFS-14720
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 3.1.1
>            Reporter: Surendra Singh Lilhore
>            Assignee: hemanthboyina
>            Priority: Major
>         Attachments: HDFS-14720.001.patch
>
>
> {noformat}
> 2019-08-11 09:15:58,092 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: 
> Can't replicate block 
> BP-725378529-10.0.0.8-1410027444173:blk_13276745777_1112363330268 because 
> on-disk length 175085 is shorter than NameNode recorded length 
> 9223372036854775807.{noformat}
> If the block length is Long.MAX_VALUE, means file belongs to this block is 
> deleted from the namenode and DN got the command after deletion of file. In 
> this case command should be ignored.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to