[MAPREDUCE-3259] ContainerLocalizer should get the proper java.library.path from LinuxContainerExecutor

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.0, 2.0.0-alpha
• Fix Version/s: 0.23.0
• Component/s: mrv2, nodemanager
• Target Version/s: 0.23.0
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 25/Oct/11 10:14
• Updated: 16/Mar/15 17:57
• Resolved: 27/Oct/11 08:31

Description

As seen in MAPREDUCE-2915, java.library.path is not being passed when the LCE spawns a JVM for ContainerLocalizer.

However, unlike branch-0.20-security, the task runtime in 0.23 is unaffected by this. This is because tasks' run-time environment is specified in the launch script by client. Setting LD_LIBRARY_PATH is the primary way of specifying the locations of required native library in this case. The config property, mapreduce.admin.user.env is always set in the job environment and the default value is to add the path to the hadoop native library to LD_LABRARY_PATH.

For JVM's being launched by the hadoop system scripts, java.library.path is set.