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-1954) Improve corrupt files warning message on NameNode web UI
Date Mon, 06 Jun 2011 20:06:59 GMT

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

Konstantin Shvachko commented on HDFS-1954:

FAQ is here: [HDFS 3.15|http://wiki.apache.org/hadoop/FAQ#I_got_a_warning_on_the_NameNode_web_UI_.22WARNING_:_There_are_about_32_missing_blocks._Please_check_the_log_or_run_fsck..22_What_does_it_mean.3F].

> 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
>   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