hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.
Date Fri, 19 Apr 2013 22:35:17 GMT

     [ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xuan Gong updated YARN-561:
---------------------------

    Attachment: YARN-561.7.patch

Apply all the latest comments
Move LOCAL_DIR_ENV to Environment
Retain all the windows related code at test case TestContainerLaunch
                
> Nodemanager should set some key information into the environment of every container that
it launches.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-561
>                 URL: https://issues.apache.org/jira/browse/YARN-561
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Hitesh Shah
>            Assignee: Xuan Gong
>              Labels: usability
>         Attachments: YARN-561.1.patch, YARN-561.2.patch, YARN-561.3.patch, YARN-561.4.patch,
YARN-561.5.patch, YARN-561.6.patch, YARN-561.7.patch
>
>
> Information such as containerId, nodemanager hostname, nodemanager port is not set in
the environment when any container is launched. 
> For an AM, the RM does all of this for it but for a container launched by an application,
all of the above need to be set by the ApplicationMaster. 
> At the minimum, container id would be a useful piece of information. If the container
wishes to talk to its local NM, the nodemanager related information would also come in handy.


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