You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2011/05/19 01:36:47 UTC

[jira] [Commented] (HDFS-1954) As a user of HDFS, I want this one error message to be more useful.

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

Suresh Srinivas commented on HDFS-1954:
---------------------------------------

I am not sure adding all the reasons why the warning is printed is a good idea.

Blocks might be missing for any number of reasons - datanodes might be down, one might be using replication factor as 1 etc. Should we add all this information to the web page as well?

I think this is a good candidate for a FAQ.

> As a user of HDFS, I want this one error message to be more useful.
> -------------------------------------------------------------------
>
>                 Key: HDFS-1954
>                 URL: https://issues.apache.org/jira/browse/HDFS-1954
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: philo vivero
>            Assignee: Patrick Hunt
>         Attachments: 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