[jira] [Resolved] (MAPREDUCE-2914) Killed and Failed jobs are not handled correctly with NotRunningJobs and should be served by the History Server

["Sharad Agarwal (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sharad Agarwal resolved MAPREDUCE-2914.
---------------------------------------

    Resolution: Invalid

Application killed/failed is different from Job killed/failed. If the job is killed/failed in AM, Application state would still be successful. Successful application means AM exited gracefully after doing the unregister.
If AM is crashed or forcefully killed, in that case history file is not consistent. So history server can't serve the requests.

Please feel free to reopen if you disagree.

> Killed and Failed jobs are not handled correctly with NotRunningJobs and should be served by the History Server
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2914
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2914
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Jeffrey Naisbitt
>
> Jobs that are that are killed or failed should be served by historyServer rather than returning the "singleton" NotRunningJob instance for that state.  Otherwise, if someone does a getJob() on a killed/failed job, he won't get the correct information at all.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira