[jira] [Commented] (MAPREDUCE-5502) History link in resource manager is broken for KILLED jobs

["Jason Lowe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763648#comment-13763648 ] 

Jason Lowe commented on MAPREDUCE-5502:
---------------------------------------

A Status/FinalStatus of KILLED/KILLED means the job was killed in the YARN sense (i.e.: the RM killed the application), while a FINISHED/KILLED state means the job was killed in the MapReduce sense.

The MapReduce ApplicationMaster is responsible for creating the MapReduce history of the job, as the YARN framework has no knowledge of MapReduce and cannot generate it on the application's behalf.  If the job is killed in the YARN sense, the AM is killed before it has a chance to create the history.  It may even be killed before the app even gets allocated resources and runs.  Unless YARN is extended to provide something like a cleanup task to run on KILLED applications, this isn't something MapReduce can solve in general.

I suspect the instances where the app ends up in KILLED/KILLED are where the job was killed before it ever had a chance to start running.  If the application had been running for some time yet a mapred -kill ended up killing it in the YARN sense, that would be a bit odd.
                
> History link in resource manager is broken for KILLED jobs
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-5502
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.5-alpha
>            Reporter: Vrushali C
>              Labels: ui
>
> History link in resource manager is broken for KILLED jobs.
> Seems to happen with jobs with State 'KILLED' and FinalStatus 'KILLED'. If the State is 'FINISHED' and FinalStatus is 'KILLED', then the "History" link is fine.
> It isn't easy to reproduce the problem since the time at which the app is killed determines the state it ends up in, which is hard to guess. these particular jobs seem to get a Diagnostics message of "Application killed by user." where as the other killed jobs get " Kill Job received from client job_1378766187901_0002
> Job received Kill while in RUNNING state. "

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira