You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2006/05/23 20:47:30 UTC
[jira] Updated: (HADOOP-240) namenode should not log failed mkdirs
at warning level
[ http://issues.apache.org/jira/browse/HADOOP-240?page=all ]
Hairong Kuang updated HADOOP-240:
---------------------------------
Attachment: mkdir.patch
This patch fixes the problem by removing the logging when a namenode "fails" to create a parent directory. It also adjusts the logging level of some logs.
> namenode should not log failed mkdirs at warning level
> ------------------------------------------------------
>
> Key: HADOOP-240
> URL: http://issues.apache.org/jira/browse/HADOOP-240
> Project: Hadoop
> Type: Bug
> Components: dfs
> Versions: 0.2.1
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Priority: Minor
> Attachments: mkdir.patch
>
> when a namenode creates a directory, it also recursively tries to creates its parent directories. If they already exist, the lastSuccess is false and the "error" is logged at the warning level.
> The right approach is to set the logging leve lower to fine or simply ignore the the "error".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira