hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8316) Audit logging should be disabled by default
Date Fri, 11 May 2012 16:06:49 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Eli Collins updated HADOOP-8316:

    Attachment: hadoop-8316.txt

Patch attached. 

- update hadoop.security.logger to NullAppender in log4j.properties, it is set explicitly
by default in the bin and env scripts, so this is mostly a nop
- hdfs/mapred.audit.logger and now default to the NullAppender in log4j.properties. Update
hdfs.audit.logger in hadoop-env.sh to match. This is being made configurable in HADOOP-8224.
mapred.audit.logger is not set in the bin or env scripts and is dead code, filed HADOOP-8392
for that (and to hookup RM/NM).

Testing, verified the hdfs audit log is no longer automatically created and logged to when
run from a tarball install.
> Audit logging should be disabled by default
> -------------------------------------------
>                 Key: HADOOP-8316
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8316
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 2.0.0
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hadoop-8316.txt
> HADOOP-7633 made hdfs, mr and security audit logging on by default (INFO level) in log4j.properties
used for the packages, this then got copied over to the non-packaging log4j.properties in
HADOOP-8216 (which made them consistent).
> Seems like we should keep with the v1.x setting which is disabled (WARNING level) by
default. There's a performance overhead to audit logging, and HADOOP-7633 provided not rationale
(just "We should add the audit logs as part of default confs") as to why they were enabled
for the packages.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message