[
https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041940#comment-13041940
]
Konstantin Shvachko commented on HDFS-1954:
-------------------------------------------
On my cluster the site "hadoop.apache.org" may not be accessible. So this is
going to be reported as a broken link.
> This gives new users some concrete help, advanced users can easily ignore it.
So it will help a new user once and then he will annoyed for the rest of his
life.
The hint you provided in the patch describes only one of many problems that can
result in missing blocks in specific system setup.
I think clarifying what a user should do to identify missing blocks is a good
starting point, which will lead him to replicas, and particularly to
{{dfs.datanode.data.dir}}.
Can we just stick to this change and not provide any other links or hints?
This was intended as a simple fix.
I can contribute a FAQ.
> Improve corrupt files warning message
> -------------------------------------
>
> Key: HDFS-1954
> URL: https://issues.apache.org/jira/browse/HDFS-1954
> Project: Hadoop HDFS
> Issue Type: Improvement
> 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 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
