[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622823#comment-13622823
 ] 

Ravi Prakash commented on MAPREDUCE-3949:
-----------------------------------------

I discussed this with Tom and Daryn.

* If the NM was able to tell the AM why its being shot, the AM could 
technically include that diagnostic message in the 
FinishApplicationMasterRequest however such a mechnanism (to tell the AM the 
reason its being shot) doesn't exist yet and would be very brittle.
* If the NM told the RM before shooting the AM, there would still be a race. 
What if the AM had completed everything it needed to do, and then got shot by 
the NM? Then the job would have been successful but be marked as FAILED by the 
RM.
* If we changed the State of a FINISHED / KILLED application to FAILED / FAILED 
on receiving RMAppAttemptEventType.CONTAINER_FINISHED, the client might still 
only get the FINISHED / KILLED message and the user would have to go to the RM 
page to see what really happened. Our current opinion is that this is probably 
the best way to go for now.

Opinions anybody?

                
> If AM fails due to overrunning resource limits, error not visible through UI 
> sometimes
> --------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3949
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3949
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.24.0, 0.23.2
>            Reporter: Todd Lipcon
>            Assignee: Ravi Prakash
>            Priority: Minor
>
> I had a case where an MR AM eclipsed the configured memory limit. This caused 
> the AM's container to get killed, but nowhere accessible through the web UI 
> showed these diagnostics. I had to go view the NM's logs via ssh before I 
> could figure out what had happened to my application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to