[
https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384373#comment-15384373
]
Jason Lowe commented on YARN-5382:
----------------------------------
I like the general idea, but I'm not sure a literal move of the audit log to
the transition will work. The audit log will try to log the remote IP of the
caller, but at the AppKilledTransition we're no longer in an RPC context so
there's no remote caller. The basic information is actually in the kill
message after YARN-5053, but not in a way that we can pull apart and pass as
individual pieces of information to the audit logger (e.g.: user, remote IP,
etc.). We could extend the kill event to optionally contain those bits then
extend the audit logger API so we can manually specify the user and remote IP
rather than have the audit logger always assume it can get them on its own.
> RM does not audit log kill request for active applications
> ----------------------------------------------------------
>
> Key: YARN-5382
> URL: https://issues.apache.org/jira/browse/YARN-5382
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.7.2
> Reporter: Jason Lowe
> Assignee: Vrushali C
> Attachments: YARN-5382-branch-2.7.01.patch,
> YARN-5382-branch-2.7.02.patch
>
>
> ClientRMService will audit a kill request but only if it either fails to
> issue the kill or if the kill is sent to an already finished application. It
> does not create a log entry when the application is active which is arguably
> the most important case to audit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
