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-475) Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment
Date Thu, 14 Mar 2013 00:48:13 GMT

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

Hitesh Shah commented on YARN-475:
----------------------------------

Both DistributedShell and UnmanagedAM use it currently but we should remove its usage as it
is definitely being set in the environment by the RM's AMLauncher.
                
> Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment
> -----------------------------------------------------------------------------------------------
>
>                 Key: YARN-475
>                 URL: https://issues.apache.org/jira/browse/YARN-475
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>
> AMs are expected to use ApplicationConstants.AM_CONTAINER_ID_ENV and derive the application
attempt id 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