[HDFS-1483] DFSClient.getBlockLocations returns BlockLocations with no indication that the corresponding blocks are corrupt

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.22.0
• Component/s: hdfs-client
• Hadoop Flags: Reviewed
• Assignee: Patrick Kling
• Reporter: Patrick Kling
• Created: 28/Oct/10 01:50
• Updated: 02/May/13 02:29
• Resolved: 17/Nov/10 05:51

Description

When there are no uncorrupted replicas of a block, FSNamesystem.getBlockLocations returns LocatedBlocks corresponding to corrupt blocks. When DFSClient converts these to BlockLocations, the information that the corresponding block is corrupt is lost. We should add a field to BlockLocation to indicate whether the corresponding block is corrupt in order to warn the client that reading this block will fail. This would be especially useful for tools such as RAID FSCK, which could then easily inspect whether data or parity blocks are corrupted without having to make direct RPC calls.

Issue Links

• depends upon: HADOOP-7013 Add boolean field isCorrupt to BlockLocation
• is depended upon by: MAPREDUCE-2156 Raid-aware FSCK