You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2009/10/01 18:41:23 UTC

[jira] Commented: (HADOOP-6294) log4j settings are service/node specific

    [ https://issues.apache.org/jira/browse/HADOOP-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761263#action_12761263 ] 

Allen Wittenauer commented on HADOOP-6294:
------------------------------------------

While attempting to create a 'universal' configuration for our nodes, I was dismayed to discover that if log4j.properties has the following enabled:

log4j.logger.org.apache.hadoop.fs.FSNamesystem.audit=INFO,DRFAAUDIT

on a client node, the hadoop will try to open/write to the audit log despite not being the namenode process.

> log4j settings are service/node specific
> ----------------------------------------
>
>                 Key: HADOOP-6294
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6294
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>
> Hadoop configuration files should be able to be shared amongst all nodes universally to ease administration pains.  Due to the way log4j initializes, log4j settings must be specific per service/node.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.