[
https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041355#comment-13041355
]
Suresh Srinivas commented on HDFS-1954:
---------------------------------------
> Do you have an alternative patch that would satisfy both the new users and
> the big cluster operators?
Yes, and that is FAQ and not namenode web UI.
The problem with this is:
* The hint that is currently added is woefully insufficient, most likely not
the problem that results in missing blocks.
* Others will continue to add information like this on to namenode web UI,
making it a mess.
Also adding exposing internal details such as "the default is typically /tmp
which is not persistent" means, if you change this behavior in the code, then
this information will be wrong. Instead, addressing Philo's other bug where
/tmp by default is not used as storage directory makes sense!
> 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
