[
https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vrushali C updated YARN-5382:
-----------------------------
Attachment: YARN-5382-branch-2.7.10.patch
YARN-5382.10.patch
Uploading v10 patch for trunk (as well as branch 2.7 for simplicity of keeping
track of patch numbers).
The only change from v9 is that the trunk patch removes the existing audit
logging in ClientRMService#forceKillApplication at the
application.isAppFinalStateStored() check.
I tried running several test jobs on my pseudo cluster and tried invoking kill
at different times, but I only see one audit log message in the RM logs.
> 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, YARN-5382-branch-2.7.05.patch,
> YARN-5382-branch-2.7.09.patch, YARN-5382-branch-2.7.10.patch,
> YARN-5382.06.patch, YARN-5382.07.patch, YARN-5382.08.patch,
> YARN-5382.09.patch, YARN-5382.10.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]
