[HDFS-7548] Corrupt block reporting delayed until datablock scanner thread detects it

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.7.0
• Target Version/s: 2.7.0
• Hadoop Flags: Reviewed
• Assignee: Rushabh Shah
• Reporter: Rushabh Shah
• Created: 18/Dec/14 16:02
• Updated: 10/Apr/15 20:29
• Resolved: 21/Jan/15 20:44

Description

When there is one datanode holding the block and that block happened to be
corrupt, namenode would keep on trying to replicate the block repeatedly but it would only report the block as corrupt only when the data block scanner thread of the datanode picks up this bad block.
Requesting improvement in namenode reporting so that corrupt replica would be reported when there is only 1 replica and the replication of that replica keeps on failing with the checksum error.

Issue Links

• relates to: HDFS-7686 Re-add rapid rescan of possibly corrupt block feature to the block scanner