[HDFS-14720] DataNode shouldn't report block as bad block if the block length is Long.MAX_VALUE.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.1
• Fix Version/s: 3.3.0, 3.1.4, 3.2.2
• Component/s: datanode
• Assignee: Hemanth Boyina
• Reporter: Surendra Singh Lilhore
• Created: 12/Aug/19 06:30
• Updated: 09/Nov/19 17:15
• Resolved: 09/Nov/19 17:15

Description

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.

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.

Issue Links

• is duplicated by: HDFS-13638 DataNode Can't replicate block because NameNode thinks the length is 9223372036854775807
• is related to: HDFS-10453 ReplicationMonitor thread could stuck for long time due to the race between replication and delete of same file in a large cluster.
• is related to: HDFS-13663 Should throw exception when incorrect block size is set
• relates to: HDFS-14794 [SBN read] reportBadBlock is rejected by Observer.