[YARN-3626] On Windows localized resources are not moved to the front of the classpath when they should be

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: yarn

Environment

Windows

• Hadoop Flags: Reviewed
• Assignee: Craig Welch
• Reporter: Craig Welch
• Created: 11/May/15 23:12
• Updated: 06/Jan/17 01:31
• Resolved: 27/May/15 21:34

Description

In response to the mapreduce.job.user.classpath.first setting the classpath is ordered differently so that localized resources will appear before system classpath resources when tasks execute. On Windows this does not work because the localized resources are not linked into their final location when the classpath jar is created. To compensate for that localized jar resources are added directly to the classpath generated for the jar rather than being discovered from the localized directories. Unfortunately, they are always appended to the classpath, and so are never preferred over system resources.

Issue Links

• relates to: YARN-3685 NodeManager unnecessarily knows about classpath-jars due to Windows limitations