[
https://issues.apache.org/jira/browse/MAPREDUCE-3614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187999#comment-13187999
]
Ravi Prakash commented on MAPREDUCE-3614:
-----------------------------------------
Thanks for the pointer Sidd! :) I was running around in circles :(
Currently, if SIGKILL the application it shows up as State:FAILED &
FinalStatus:FAILED.
on SIGTERM, its State:FINISHED & FinalStatus:UNDEFINED.
Here's the ideal behavior in my mind:
1. I think a SIGTERM'd AM should lead to a State: FAILED & FinalStatus:FAILED
job (if this was the last AM attempt)
2. The history logs should be copied over to the HS every time (even if this is
NOT the last AM attempt). The Tracking UI should be active.
3. The diagnostic message which shows up in the "Note" coloumn should mention
that the AM was SIGTERMED or something to that effect.
Would you agree?
> 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
