[HDFS-10625] VolumeScanner to report why a block is found bad

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.4
• Component/s: datanode, hdfs
• Labels: supportability
• Target Version/s: 2.7.4
• Hadoop Flags: Reviewed
• Assignee: Rushabh Shah
• Reporter: Yongjun Zhang
• Created: 14/Jul/16 05:43
• Updated: 02/Oct/19 17:14
• Resolved: 29/Aug/16 21:31

Description

VolumeScanner may report:

WARN org.apache.hadoop.hdfs.server.datanode.VolumeScanner: Reporting bad blk_1170125248_96458336 on /d/dfs/dn

It would be helpful to report the reason why the block is bad, especially when the block is corrupt, where is the first corrupted chunk in the block.

Issue Links

• is duplicated by: HDFS-10626 VolumeScanner prints incorrect IOException in reportBadBlocks operation
• is related to: HDFS-10512 VolumeScanner may terminate due to NPE in DataNode.reportBadBlocks
• is related to: HDFS-10587 Incorrect offset/length calculation in pipeline recovery causes block corruption