Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 11 May 2012 16:04:50 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1306630088.54961.1336752290161.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HADOOP-8392) Add YARN audit logging to
 log4j.properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Eli Collins created HADOOP-8392:
-----------------------------------

             Summary: Add YARN audit logging to log4j.properties
                 Key: HADOOP-8392
                 URL: https://issues.apache.org/jira/browse/HADOOP-8392
             Project: Hadoop Common
          Issue Type: Improvement
    Affects Versions: 2.0.0
            Reporter: Eli Collins


MAPREDUCE-2655 added MR/NM audit logging but it's not hooked up into log4j.properties or the bin and env scripts like the other audit logs so you have to modify the deployed binary to change them. Let's add the relevant plumbing that the other audit loggers have, and update log4.properties with a sample configuration that's disabled by default, eg see [this comment|https://issues.apache.org/jira/browse/MAPREDUCE-2655?focusedCommentId=13084191&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13084191].

Also, looks like mapred.AuditLogger and its plumbing can be removed.

--
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