hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramkumar Vadali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1111) getCorruptFiles() should give some hint that the list is not complete
Date Tue, 31 Aug 2010 00:03:56 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904431#action_12904431
] 

Ramkumar Vadali commented on HDFS-1111:
---------------------------------------

The RaidNode use case at a high level is to identify corrupted data that can be fixed by using
parity data.

This can be achieved by:
 1. Getting a list of corrupt files and subsequently identifying the corrupt blocks in each
corrupt file. The current getCorruptFiles() RPC enables getting the list of corrupt files.

-OR-
 2. Getting a list of corrupt files annotated by the corrupt blocks. If this patch introduced
a RPC with that functionality, it would be an improvement over the getCorruptFiles() RPC.


I have a patch for https://issues.apache.org/jira/browse/HDFS-1171 that depends on the getCorruptFiles()
RPC, so removal of that RPC with no substitute would mean loss of functionality.

> getCorruptFiles() should give some hint that the list is not complete
> ---------------------------------------------------------------------
>
>                 Key: HDFS-1111
>                 URL: https://issues.apache.org/jira/browse/HDFS-1111
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 0.22.0
>            Reporter: Rodrigo Schmidt
>            Assignee: Sriram Rao
>             Fix For: 0.22.0
>
>         Attachments: HADFS-1111.0.patch, HDFS-1111-y20.1.patch, HDFS-1111-y20.2.patch,
HDFS-1111.trunk.patch
>
>
> If the list of corruptfiles returned by the namenode doesn't say anything if the number
of corrupted files is larger than the call output limit (which means the list is not complete).
There should be a way to hint incompleteness to clients.
> A simple hack would be to add an extra entry to the array returned with the value null.
Clients could interpret this as a sign that there are other corrupt files in the system.
> We should also do some rephrasing of the fsck output to make it more confident when the
list is not complete and less confident when the list is known to be incomplete.

-- 
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