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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/06/05 23:21:30 UTC
[jira] Commented: (HADOOP-240) namenode should not log failed
mkdirs at warning level
[ http://issues.apache.org/jira/browse/HADOOP-240?page=comments#action_12414859 ]
Doug Cutting commented on HADOOP-240:
-------------------------------------
I'd like to apply this now, but it has conflicts. I'll try to work through them...
> 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
> Fix For: 0.3.0
> Attachments: mkdir.patch, mkdir_new.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