Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 7 Jun 2011 22:06:59 +0000 (UTC)
From: "Patrick Hunt (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1547193075.1495.1307484419272.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1301510712.21348.1305683627385.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1954) Improve corrupt files warning
 message on NameNode web UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Patrick Hunt commented on HDFS-1954:
------------------------------------

TestHDFSCLI is currently broken in trunk, not caused by this patch:
  https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Hdfs-trunk/690/testReport/junit/org.apache.hadoop.cli/TestHDFSCLI/
also TestMissingBlocksAlert is covering this change.


> 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
>         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 defined?"
> 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