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

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0-beta
• Labels: usability
• Target Version/s: 2.1.0-beta
• Hadoop Flags: Incompatible change, Reviewed
• Assignee: Xuan Gong
• Reporter: Hitesh Shah
• Created: 10/Apr/13 00:43
• Updated: 27/Aug/13 22:15
• Resolved: 24/Apr/13 00:01

Description

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.

Issue Links

• relates to: YARN-603 Create a testcase to validate Environment.MALLOC_ARENA_MAX
• relates to: YARN-604 The checkers in the MRAppMaster should validate everything that the NM is supposed to be setting in the env
• relates to: MAPREDUCE-5175 Update MR App to not set envs that will be set by NMs anyways after YARN-561
• relates to: YARN-602 NodeManager should mandatorily set some Environment variables into every containers that it launches