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 "Zhijie Shen (JIRA)" <ji...@apache.org> on 2015/05/01 22:56:06 UTC

[jira] [Resolved] (HADOOP-8392) Add YARN audit logging to log4j.properties

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

Zhijie Shen resolved HADOOP-8392.
---------------------------------
    Resolution: Duplicate

It sounds a YARN issue. There already exists a YARN jira: YARN-2255. So close this jira as duplicate of that one.

> 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-alpha
>            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 was sent by Atlassian JIRA
(v6.3.4#6332)