You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Shvachko (Jira)" <ji...@apache.org> on 2019/10/31 23:14:00 UTC
[jira] [Commented] (HDFS-14720) DataNode shouldn't report block as
bad block if the block length is Long.MAX_VALUE.
[ https://issues.apache.org/jira/browse/HDFS-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964438#comment-16964438 ]
Konstantin Shvachko commented on HDFS-14720:
--------------------------------------------
Hey guys, could you explain how this fixes the {{reportBadBlock()}} issue from HDFS-14794?
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org