[
https://issues.apache.org/jira/browse/HDFS-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Chu updated HDFS-4048:
------------------------------
Attachment: HDFS-4048.patch.trunk.2
HDFS-4048.patch.branch-2.2
Attached HDFS-4048.patch.branch-2.2 and HDFS-4048.patch.trunk.2.
I changed the log level to WARN. I also changed the INFO log in
FsVolumeList#checkDirs to WARN.
> Use ERROR instead of INFO for volume failure logs
> -------------------------------------------------
>
> Key: HDFS-4048
> URL: https://issues.apache.org/jira/browse/HDFS-4048
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha
> Reporter: Stephen Chu
> Assignee: Stephen Chu
> Fix For: 3.0.0, 2.0.3-alpha
>
> Attachments: HDFS-4048.patch.branch-2, HDFS-4048.patch.branch-2.2,
> HDFS-4048.patch.trunk, HDFS-4048.patch.trunk.2
>
>
> I misconfigured the permissions of the DataNode data directories (they were
> owned by root, instead of hdfs).
> I wasn't aware of this misconfiguration until a few days later. I usually
> search through the logs for WARN and ERROR but didn't find messages at these
> levels that indicated volume failure.
> After more carefully reading the logs, I found:
> {code}
> 2012-10-01 13:07:10,440 INFO org.apache.hadoop.hdfs.server.common.Storage:
> Cannot access storage directory /data/4/dfs/dn
> 2012-10-01 13:07:10,440 INFO org.apache.hadoop.hdfs.server.common.Storage:
> Storage directory /data/4/dfs/dn does not exist.
> {code}
> I think we should bump the log level to ERROR. This will make the problem
> more visible to users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
