[
https://issues.apache.org/jira/browse/MAPREDUCE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184421#comment-13184421
]
Ravi Prakash commented on MAPREDUCE-3614:
-----------------------------------------
Hmm... Who knew, but the world is more complicated than what I first thought. I
think in the AM shutdown hook
{noformat}
Runtime.getRuntime().addShutdownHook(
new CompositeServiceShutdownHook(appMaster));
{noformat}
we need a more elaborate shutdown hook. It should send a JobFinishEvent for the
AM to handle so that the normal course of a job finish is followed, albeit for
a failed job. That way, the history server should also get to know about this
job. Currently, the HS has no knowledge of jobs killed using SIGTERM / SIGKILL.
SIGKILL terminated jobs will continue to not be picked by the HS, but atleast
SIGTERM we can include.
If anybody has useful input on this design, please let me know
> finalState UNDEFINED if AM is killed by hand
> --------------------------------------------
>
> Key: MAPREDUCE-3614
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3614
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Attachments: MAPREDUCE-3614.branch-0.23.patch
>
>
> Courtesy [~dcapwell]
> {quote}
> If the AM is running and you kill the process (sudo kill #pid), the State in
> Yarn would be FINISHED and FinalStatus is UNDEFINED. The Tracking UI would
> say "History" and point to the proxy url (which will redirect to the history
> server).
> The state should be more descriptive that the job failed and the tracker url
> shouldn't point to the history server.
> {quote}
--
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
