[
https://issues.apache.org/jira/browse/MAPREDUCE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-2795:
-----------------------------------------------
Status: Open (was: Patch Available)
The patch has got it wrong.
Application is a YARN level concept, while Job is a MapReduce concept. When a
mapreduce job is killed, it goes through the AM. So for the platform(aka YARN),
the application finished cleanly even though the job itself is killed by the
user.
I see that AppsKilled is updated correctly, only when an application is
forcefully terminated on the RM via ClientRMProtocol.forceKillApplication(). If
you want to figure out the number of killed jobs, you should go to the
JobHistoryServer.
If you are satisfied with the explanation, please close the ticket as invalid.
Thanks.
> [MR-279] AppsKilled is never incremented
> ----------------------------------------
>
> Key: MAPREDUCE-2795
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2795
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Devaraj K
> Priority: Blocker
> Fix For: 0.23.0, 0.24.0
>
> Attachments: MAPREDUCE-2795.patch
>
>
> AppsKilled metrics is never incremented even though there are killed jobs in
> the system.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
