[
https://issues.apache.org/jira/browse/MAPREDUCE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-2952:
-----------------------------------------------
Component/s: (was: client)
Description: When Container crashes, the reason for failures isn't
propagated because of a bug in _RMAppAttemptImpl.AMContainerCrashedTransition_
which simply discards the diagnostics of the container. Also
RMAppAttemptImpl.diagnostics is never consumed. (was: 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.)
Summary: Application failure diagnostics are not consumed in a couple
of cases (was: JobClient doesn't show the reason why AM crashed)
> Application failure diagnostics are not consumed in a couple of cases
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-2952
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2952
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Fix For: 0.23.0
>
>
> When Container crashes, the reason for failures isn't propagated because of a
> bug in _RMAppAttemptImpl.AMContainerCrashedTransition_ which simply discards
> the diagnostics of the container. Also RMAppAttemptImpl.diagnostics is never
> consumed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
