hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1954) Improve corrupt files warning message on NameNode web UI
Date Tue, 07 Jun 2011 20:17:59 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Patrick Hunt updated HDFS-1954:

    Attachment: HDFS-1954.patch

This updated patchremoves the hint, other updates to the patch as we discussed in the comment
stream. (Thanks for the FAQ update Konstantin!)

Note that this can only be applied to trunk. The reason why the 22 build failed (HDFS-2013)
is that the test for this issue "TestMissingBlocksAlert" is different in 22 vs trunk. In 22
it checks for "There are about #" while trunk checks for "There are #" missing blocks. This
test passes for me on trunk with this updated patch. I also verified by running the test by
hand through the UI interface.

> Improve corrupt files warning message on NameNode web UI
> --------------------------------------------------------
>                 Key: HDFS-1954
>                 URL: https://issues.apache.org/jira/browse/HDFS-1954
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: philo vivero
>            Assignee: Patrick Hunt
>             Fix For: 0.22.0
>         Attachments: HDFS-1954.patch, HDFS-1954.patch, HDFS-1954.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> On NameNode web interface, you may get this warning:
>   WARNING : There are about 32 missing blocks. Please check the log or run fsck.
> If the cluster was started less than 14 days before, it would be great to add: "Is dfs.data.dir
> If at the point of that error message, that parameter could be checked, and error made
"OMG dfs.data.dir isn't defined!" that'd be even better. As is, troubleshooting undefined
parameters is a difficult proposition.
> I suspect this is an easy fix.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message