hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-944) App failed with container launch failed even though container started
Date Tue, 23 Jul 2013 19:00:50 GMT

    [ https://issues.apache.org/jira/browse/YARN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717481#comment-13717481

Hitesh Shah commented on YARN-944:

There are 2 different issues being reported in this jira: 

  - The first related to the underlying error which is due to the changes in YARN-701, default
addresses of combined with the use of ip in the tokens cause apps to fail. 
  - the second issue is related to what failure information is propagated back to the user.
For any non-zero exit code, the user now sees a ShellExitCodeException - this change was done
as part of YARN-814.


> 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
>         Attachments: nm.log, rm.log, 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

View raw message