[
https://issues.apache.org/jira/browse/YARN-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380047#comment-15380047
]
Vrushali C edited comment on YARN-5382 at 7/15/16 8:27 PM:
-----------------------------------------------------------
Thanks [~jlowe]! Uploading patch v2 which uses RMAuditLogger.
But with this, I now see two exactly same log messages in the RM log since the
forceKillApplication function is entered twice.
I was wondering if the message can be made slightly different? But that would
mean adding something to RMAuditLogger itself to log a different style of
message.
>From my pseudo-distributed setup:
{code}
[hadoop-2.7.4-SNAPSHOT (branch-2.7)]$ grep -rni ClientRMService
logs/yarn-vchannapattan-resourcemanager-cchannapattan.log | grep "Kill App" |
grep application_1468608647317_0001
logs/yarn-vchannapattan-resourcemanager-channapattan.log:348:2016-07-15
11:51:10,773 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=vchannapattan IP=127.0.0.1 OPERATION=Kill Application Request
TARGET=ClientRMService-11 RESULT=SUCCESS
APPID=application_1468608647317_0001
logs/yarn-vchannapattan-resourcemanager-tw-mbp13-channapattan.log:387:2016-07-15
11:51:10,987 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=vchannapattan IP=127.0.0.1 OPERATION=Kill Application Request
TARGET=ClientRMService RESULT=SUCCESS APPID=application_1468608647317_0001
[ hadoop-2.7.4-SNAPSHOT (branch-2.7)]$
{code}
was (Author: vrushalic):
Thanks [~jlowe]! Uploading patch v2 which uses RMAuditLogger.
But with this, I now see two exactly same log messages in the RM log since the
forceKillApplication function is entered twice.
I was wondering if the message can be made slightly different? But that would
mean adding something to RMAuditLogger itself to log a different style of
message.
>From my pseudo-distributed setup:
{code}
[hadoop-2.7.4-SNAPSHOT (branch-2.7)]$ grep -rni ClientRMService
logs/yarn-vchannapattan-resourcemanager-vchannapattan.log | grep
application_1468608647317_0001
logs/yarn-vchannapattan-resourcemanager-channapattan.log:298:2016-07-15
11:50:58,702 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=vchannapattan IP=127.0.0.1 OPERATION=Submit Application Request
TARGET=ClientRMService RESULT=SUCCESS APPID=application_1468608647317_0001
logs/yarn-vchannapattan-resourcemanager-vchannapattan.log:348:2016-07-15
11:51:10,773 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=vchannapattan IP=127.0.0.1 OPERATION=Kill Application Request
TARGET=ClientRMService-11 RESULT=SUCCESS
APPID=application_1468608647317_0001
logs/yarn-vchannapattan-resourcemanager-channapattan.log:387:2016-07-15
11:51:10,987 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=vchannapattan IP=127.0.0.1 OPERATION=Kill Application Request
TARGET=ClientRMService RESULT=SUCCESS APPID=application_1468608647317_0001
[tw-mbp13-channapattan hadoop-2.7.4-SNAPSHOT (branch-2.7)]$
{code}
> 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]
