[YARN-593] container launch on Windows does not correctly populate classpath with new process's environment variables and localized resources

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta
• Component/s: nodemanager
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 19/Apr/13 17:02
• Updated: 12/May/16 18:30
• Resolved: 19/Apr/13 19:33

Description

On Windows, we must bundle the classpath of a launched container in an intermediate jar with a manifest. Currently, this logic incorrectly uses the nodemanager process's environment variables for substitution. Instead, it needs to use the new environment for the launched process. Also, the bundled classpath is missing some localized resources for directories, due to a quirk in the way File#toURI decides whether or not to append a trailing '/'.

Issue Links

• is part of: YARN-191 Enhancements to YARN for Windows Server and Windows Azure development and runtime environments
• is related to: HADOOP-9488 FileUtil#createJarWithClassPath only substitutes environment variables from current process environment/does not support overriding when launching new process
• is related to: MAPREDUCE-4987 TestMRJobs#testDistributedCache fails on Windows due to classpath problems and unexpected behavior of symlinks