You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/04/10 19:46:16 UTC

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

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

Hitesh Shah commented on YARN-561:
----------------------------------

Follow-up would be to change the MR AM to rely on these settings instead of duplicating them when launching its containers.
                
> 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: Omkar Vinit Joshi
>              Labels: usability
>
> 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