[
https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388954#comment-15388954
]
Sunil G commented on YARN-5382:
-------------------------------
Hi [~vrushalic]
Thanks for updating the patch. I think there is a slight misunderstanding, I
guess my comment was not very clear. What I was trying convey is that If we
choose to use {{RMAppKillEvent}} for all cases, I think for internal kill
events (within scheduler such as {{AbstractYarnScheduler}} and
{{CapacityScheduler}}) we do not need to do audit logging. So we can either
pass a flag to log or can pass username/ip as empty to take the logging
decision.
I think for internal scheduler kill events, we will not be able to derive
username or remote ip correctly as its not user driven. Thoughts?
> 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, YARN-5382-branch-2.7.03.patch,
> YARN-5382-branch-2.7.04.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]
