[
https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041998#comment-13041998
]
Patrick Hunt commented on HDFS-1954:
------------------------------------
{quote}
Can we just stick to this change and not provide any other links or hints?
I can contribute a FAQ.
{quote}
I think a FAQ entry would be a great help to users. As I mentioned if that
existed this change would probably have gone a lot smoother. :-)
Makes sense to drop the hint given we'd have a proper writeup. I would like to
just reference the existence of a FAQ instead, no link but just something like
"<small>See the Hadoop FAQ for common causes and potential solutions</small>"
or somesuch. This would only be displayed in the error case, not all the time.
That sound reasonable?
> 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
