hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Kling (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1483) DFSClient.getBlockLocations returns BlockLocations with no indication that the corresponding blocks are corrupt
Date Wed, 03 Nov 2010 04:12:26 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Kling updated HDFS-1483:
--------------------------------

    Attachment: HDFS-1483.patch

Review board: https://reviews.apache.org/r/27/

> 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
>         Attachments: 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.


Mime
View raw message