[
https://issues.apache.org/jira/browse/MAPREDUCE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100239#comment-13100239
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2952:
----------------------------------------------------
Also, the case when Container crashes, the reason isn't propagated because of a
bug in _RMAppAttemptImpl.AMContainerCrashedTransition_ which simply discards
the diagnostics of the container. Also _RMAppAttemptImpl.diagnostics_ is also
never consumed.
> JobClient doesn't show the reason why AM crashed
> ------------------------------------------------
>
> Key: MAPREDUCE-2952
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2952
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
>
> When MR ApplicationMaster crashes, say because of a localization error, NM
> promptly reports the exception trace to the RM via diagnostics. Client
> eventually figures out that the application has failed, but it never prints
> the reason.
> The reason for failure is already propagated to the client in most cases via
> _ApplicationReport_ but it isn't printed/logged.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
