[
https://issues.apache.org/jira/browse/MAPREDUCE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210681#comment-13210681
]
Ravi Prakash commented on MAPREDUCE-3614:
-----------------------------------------
I just IMd with Vinod. Here's the lowdown:
In the JobHistoryEventHandler
1. We can't take a long time in the shutdown hook. So we cannot drain the
entire event queue. The size of the queue might be proportional to the job
(which might be big)
2. In case of SIGTERM, we can throw away all the events, process a single job
finish event, move the history files to the done location and then exit.
Also, originally the plan was to have multiple jobs per AM, but that got
deprioritized, so if we can prevent storing the JobIds, that'd be good, but if
no other alternative is present, then it is fine.
> 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
