[
https://issues.apache.org/jira/browse/MAPREDUCE-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594818#comment-13594818
]
Jason Lowe commented on MAPREDUCE-4993:
---------------------------------------
Setting the diagnostics isn't sufficient if we then continue to throw the
exception. As mentioned above, the exception ends up bubbling all the way up
to the AsyncDispatcher handler thread which forcibly exits the process. That's
not good and leads to a misleading status like KILLED. There needs to be
better exception handling as well as diagnostics.
> AM thinks it was killed when an error occurs setting up a task container
> launch context
> ---------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4993
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4993
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.0.3-alpha, 0.23.5
> Reporter: Jason Lowe
> Assignee: Abhishek Kapoor
>
> If an IOException occurs while setting up a container launch context for a
> task then the AM exits with a KILLED status and no diagnostics. The job
> should be marked as FAILED (or maybe ERROR) with a useful diagnostics message
> indicating the nature of the error.
--
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
