hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly
Date Tue, 26 Mar 2013 02:39:15 GMT

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

Bikas Saha commented on YARN-498:
---------------------------------

Committed to trunk and branch-2
                
> Unmanaged AM launcher does not set various constants in env for an AM, also does not
handle failed AMs properly
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-498
>                 URL: https://issues.apache.org/jira/browse/YARN-498
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>         Attachments: YARN-498.1.patch, YARN-498.2.patch, YARN-498.3.patch, YARN-498.4.patch,
YARN-498.wip.patch
>
>
> Currently, it only sets the app attempt id which is really not required as AMs are only
expected to extract it from the container id.

--
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

Mime
View raw message