[ https://issues.apache.org/jira/browse/HDFS-14720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970878#comment-16970878 ]
Hudson commented on HDFS-14720: ------------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17622 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17622/]) HDFS-14720. DataNode shouldn't report block as bad block if the block (surendralilhore: rev 320008bb7cc558b1300398178bd2f48cbf0b6c80) * (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/ReplicationWork.java > 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, HDFS-14720.002.patch, > HDFS-14720.003.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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org