[
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 patch adds some detail to the error message, we can't check the setting as
that's local to the datanode, and not available on this screen/node.
It now says something like (with the hint class=small):
WARNING : There are 5 missing blocks. Please check the log or run fsck.
Hint: A common mis-configuration is not overriding "dfs.datanode.data.dir" on
all datanodes(the default is typically /tmp which is not persistent)
> 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
