MR AM can change to SUCCESS state but crash and fail to write JobHistory
------------------------------------------------------------------------
Key: MAPREDUCE-3559
URL: https://issues.apache.org/jira/browse/MAPREDUCE-3559
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mr-am, mrv2
Affects Versions: 0.23.0
Reporter: Vinod Kumar Vavilapalli
In such corner cases, clients can see that the job has become successful but
they cannot get any information from JobHistoryServer. And there is no means of
figuring out what happened in the system except from the AM logs.
Ideally we should set the JobState to become SUCCESS as the last step, once
everything else is done. The code changes may be a bit complicated to achieve
this, but we can investigate and see.
--
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
