hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "philo vivero (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1954) As a user of HDFS, I want this one error message to be more useful.
Date Wed, 18 May 2011 23:56:47 GMT

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

philo vivero commented on HDFS-1954:

Don't let perfect destroy good. Warning already suggests to check logs and run fsck, yet we
know anyone who sets up HDFS with defaults will get this corruption eventually. It's reasonable
to have an error message suggest the most common cause of the error, if the error cannot be
eliminated in the first place.

If you must eliminate suggestions, then make the error message Very Google Searchable, and
let people know the common causes of the error on the resulting page (it appears the FAQ is
the page you're suggesting here).

Perhaps: "WARNING: There are missing blocks in your filesystem. Please locate the HDFS FAQ
to help determine causes of this problem. Number of missing blocks: #####."

Then put that exact verbiage on the FAQ, too, so people will find it when searching. Note
that I've put the variable part of the error at the very end.

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