[
https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated HDFS-1954:
-------------------------------
Status: Patch Available (was: Open)
Thanks for the feedback guys. I agree what you are suggesting is better than
what I came up with. However I did think about such solutions and ended up
deciding not to make such changes for this specific jira, a summary why:
1) Originally I nearly implemented what Suresh suggests, which is a great idea,
but decided against it because of the reason Todd mentioned (offline
deployments), the fact that no such faq already existed (I checked both the faq
and the troubleshooting guide on the wiki), and finally because afaict none of
the existing screens are linking out to such docs. I didn't want to introduce
new functionality here, just address the jira.
2) newbie users are the most likely to make this mistake. If you're more
experience with hadoop you're also more likely to know what other issues could
have caused this, or at least where to look. So having a big long list didn't
seem that important.
3) I could have introduced a new "faq" page, however I decided against that
because I didn't want to duplicate information that rightly should be in the
wiki (faq).
4) I had limited time, I'm a hadoop "newbie", I wanted to address the issue at
hand. Philo's comment "perfect enemy of good".
I'd be happy if someone else were to create another jira that addresses this at
a higher level (adds a faq, external links, whatever) and as a results wipes
out my change, but short of that happening I'll re-submit this as a short term
fix. If it doesn't meet your approval at least I can say I tried. Thanks!
> 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
> 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
