[
https://issues.apache.org/jira/browse/HDFS-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882780#action_12882780
]
Konstantin Shvachko commented on HDFS-1111:
-------------------------------------------
> If I remember correctly, there is another message
So what exactly will it print under the conditions (of your example) above?
I see that {{getCorruptFiles()}} was introduced in HDFS-729 as a part of fsck
changes related to -list-corruptfiles. And it is not necessary for fsck. Do you
agree with that?
RaidNode has not been mentioned before, not here, not in HDFS-729.
ClientProtocol is HDFS-private api according to recently adopted
classification. This means that external tools should not use or depend on it.
> 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
> Reporter: Rodrigo Schmidt
> Assignee: Rodrigo Schmidt
> Attachments: HADFS-1111.0.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.
