[
https://issues.apache.org/jira/browse/MAPREDUCE-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084118#comment-13084118
]
Thomas Graves commented on MAPREDUCE-2655:
------------------------------------------
Going to add a RMAuditLogger class that has methods to log success/failure
similar to jobtracker Auditlogger class.
Certain of these don't make sense to log since the authentication will throw
away unauthorized requests.
Right now I plan on logging the following things:
RM:
- all refresh commands - success and failure
- Application submissions
- Application kills
- AM registrations - failure and success
- illegal container allocations from AM - invalid container id or container not
owned by App
- successful container allocations and deallocations from AM
NM:
- Container allocation successes
> 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
