hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2655) MR279: Audit logs for YARN
Date Fri, 12 Aug 2011 15:33:27 GMT

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

Thomas Graves commented on MAPREDUCE-2655:
------------------------------------------

Example on how you would config for rm and nm audit logs:

rm.audit.logger=INFO,RMAUDIT
log4j.logger.org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger=${rm.audit.logger}
log4j.additivity.org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger=false
log4j.appender.RMAUDIT=org.apache.log4j.DailyRollingFileAppender
log4j.appender.RMAUDIT.File=${hadoop.log.dir}/rm-audit.log
log4j.appender.RMAUDIT.layout=org.apache.log4j.PatternLayout
log4j.appender.RMAUDIT.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n
log4j.appender.RMAUDIT.DatePattern=.yyyy-MM-dd

nm.audit.logger=INFO,NMAUDIT
log4j.logger.org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger=${nm.audit.logger}
log4j.additivity.org.apache.hadoop.yarn.server.nodemanager.NMAuditLogger=false
log4j.appender.NMAUDIT=org.apache.log4j.DailyRollingFileAppender
log4j.appender.NMAUDIT.File=${hadoop.log.dir}/nm-audit.log
log4j.appender.NMAUDIT.layout=org.apache.log4j.PatternLayout
log4j.appender.NMAUDIT.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n
log4j.appender.NMAUDIT.DatePattern=.yyyy-MM-dd

> MR279: Audit logs for YARN 
> ---------------------------
>
>                 Key: MAPREDUCE-2655
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2655
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>
> We need audit logs for YARN components:
> ResourceManager:
>  - All the refresh* protocol access points - refreshQueues, refreshNodes, refreshProxyUsers,
> refreshUserToGroupMappings.
>  - All app-submissions, app-kills to RM.
>  - Illegal and successful(?) AM registrations.
>  - Illegal container allocations/deallocations from AMs
>  - Successful container allocations/deallocations from AMs too?
> NodeManager:
>  - Illegal container launches from AMs
>  - Successful container launches from AMs too?
> Not sure if we need audit logs from MR AMs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message