[
https://issues.apache.org/jira/browse/HDFS-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858022#action_12858022
]
Rodrigo Schmidt commented on HDFS-1031:
---------------------------------------
I'm sorry I'm a little late on this discussion, but I don't agree with Eli's
comment on the message when corruptFileCount == 0. The API nn.getCorruptFiles()
is based on the list of blocks that need replication and might not be
up-to-date (HDFS-729). For instance, I think it returns 0 if the namenode is on
safe mode. We had a similar discussion on HDFS-1032 and we decided to go for
the message André had before ("unable to locate any"-style). Maybe we should
use something in between "100% guaranteed it's safe" and "Please don't trust
me".
What about "No missing blocks found at the moment. Please run fsck for a
thorough health analysis." ?
> Enhance the webUi to list a few of the corrupted files in HDFS
> --------------------------------------------------------------
>
> Key: HDFS-1031
> URL: https://issues.apache.org/jira/browse/HDFS-1031
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: dhruba borthakur
> Assignee: André Oriani
> Attachments: hdfs-1031_aoriani.patch, hdfs-1031_aoriani_2.patch,
> hdfs-1031_aoriani_3.patch
>
>
> The existing webUI displays something like this:
> WARNING : There are about 12 missing blocks. Please check the log or run
> fsck.
> It would be nice if we can display the filenames that have missing blocks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
