[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved YARN-561. ------------------------------------------ Resolution: Fixed Fix Version/s: 2.0.5-beta Hadoop Flags: Incompatible change,Reviewed branch-2 patch looks good too. +1. Committed this to trunk and branch-2. Thanks Xuan. Marking this as incompatible, as it is renaming the LOCAL_DIRS env constant. > 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 > Fix For: 2.0.5-beta > > Attachments: YARN-561.10.patch, YARN-561.11.patch, > YARN-561.12.branch_2.patch, YARN-561.13.branch-2.patch, 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, YARN-561.8.patch, YARN-561.9.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