hadoop-hdfs-issues mailing list archives

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

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

Konstantin Shvachko commented on HDFS-1111:
-------------------------------------------

This 2 comments by [Sanjay|https://issues.apache.org/jira/browse/HDFS-1111?focusedCommentId=12883369&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12883369]
and [me|https://issues.apache.org/jira/browse/HDFS-1111?focusedCommentId=12893457&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12893457]
should summarize the discussion about ClientProtocol changes.
ClientProtocol, DFSClient, DistributedFileSystem, FileSystem, FileContect... - this classes
may be affected by the changes. 
The main problem is that
- there is no clear idea / description of how this api will be exposed to RaidNode,
- therefore, it is not clear what is the scope of the changes,
- the changes intended for RaidNode are not related to Fsck, and shouldn't be mixed in with
this functionality.

You say (plural) tools, do you have other than RaidNode tools in mind?

> 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