[
https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041894#comment-13041894
]
Patrick Hunt commented on HDFS-1954:
------------------------------------
@suresh I agree that it would be good to find a better solution. That's why I
responded to your comments. My feeling (granted I could be wrong) was that the
user had a point - that it would be nice to give some insight into what might
be wrong and where to look for more detail. If a FAQ existed I would likely
have addressed this differently.
@konstantin (hi!) - this only shows up when a problem occurs, not all the time.
So it would only be annoying when you have a real problem. Giving more insight
at that time seems like it would be helpful/useful.
As I said previously, if you know the "right way" feel free to overwrite my
changes to make it better. I was only trying to make it so.
> 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
