[
https://issues.apache.org/jira/browse/YARN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-944:
-------------------------
Attachment: YARN-944.patch
Today when MapReduce launches a container, Container errors are redirected to
syserr file under container log directory, we are not able to view that in NM
log. In case of container-launch error(the error after user process is
launched), users now will always see ShellExitCodeException in NM log, and the
detailed message can be retrieved from container log in web UI. YARN-814 fixed
the case that the error before user process is launched will be logged both in
NM log and container log.
For other applications on YARN that are not redirecting stderr, user can see
the container errors both in NM log and container log.
Uploaded a patch to update the logging error message.
> App failed with container launch failed even though container started
> ---------------------------------------------------------------------
>
> Key: YARN-944
> URL: https://issues.apache.org/jira/browse/YARN-944
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Bikas Saha
> Assignee: Omkar Vinit Joshi
> Priority: Blocker
> Attachments: nm.log, rm.log, YARN-944.patch, yarn-site.xml
>
>
> The container is the AM container. It started and the AM failed during RM
> registration. The error message presented was about container launch failing.
--
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
