[
https://issues.apache.org/jira/browse/MAPREDUCE-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-2914:
-----------------------------------------------
Description:
For apps(not jobs) which are killed/failed, JobHistory is most likely garbled.
We still need to make sure that JobStatus fields like user, jobName, jobFile,
trackingUrl etc are correct for jobs whose corresponding apps got killed/failed.
was:
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.
Priority: Minor (was: Major)
Summary: MR jobs with the corresponding apps Killed or Failed have
insufficient information in their JobStatuses (was: Killed and Failed jobs are
not handled correctly with NotRunningJobs and should be served by the History
Server)
> MR jobs with the corresponding apps Killed or Failed have insufficient
> information in their JobStatuses
> -------------------------------------------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> For apps(not jobs) which are killed/failed, JobHistory is most likely garbled.
> We still need to make sure that JobStatus fields like user, jobName, jobFile,
> trackingUrl etc are correct for jobs whose corresponding apps got
> killed/failed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
