[
https://issues.apache.org/jira/browse/HDFS-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang resolved HDFS-1483.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.22.0
Hadoop Flags: [Reviewed]
I've just committed this. Thanks Patrick!
> DFSClient.getBlockLocations returns BlockLocations with no indication that
> the corresponding blocks are corrupt
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-1483
> URL: https://issues.apache.org/jira/browse/HDFS-1483
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs client
> Reporter: Patrick Kling
> Assignee: Patrick Kling
> Fix For: 0.22.0
>
> Attachments: HDFS-1483.2.patch, HDFS-1483.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
