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

Hudson commented on HADOOP-8316:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk #1077 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1077/])
    HADOOP-8316. Audit logging should be disabled by default. Contributed by 
Eli Collins (Revision 1337334)

     Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1337334
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/conf/log4j.properties
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/hadoop-env.sh
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/log4j.properties

                
> 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
>             Fix For: 2.0.0
>
>         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

        

Reply via email to