[
https://issues.apache.org/jira/browse/HDFS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905967#action_12905967
]
Sriram Rao commented on HDFS-1111:
----------------------------------
@Dhruba/Suresh,
Given that we need to a new API to FileSystem, that sounds like new a JIRA to
me. I'd be happy to do it. That said, I'd like to get a closure on this
issue.
@Dhruba---Since you seem to be in agreement with the changes for this JIRA, can
you make it a +1?
> 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.1.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.
