[HADOOP-1493] possible double setting of java.library.path introduced by HADOOP-838

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0
• Fix Version/s: 0.14.0
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 14/Jun/07 14:28
• Updated: 08/Jul/09 16:52
• Resolved: 18/Jun/07 20:55

Description

HADOOP-838 introduced setting java.library.path to run the TaskTracker$Child from the TaskTracker's library.path, so that the native lib path is passed to the child. However if we also want to set -Djava.library.path from the configuration by "mapred.child.java.opts", than the child java process is called with two -Djava.library.path properties, and java seems to ignore the former, rather than use the two. This situation prevents using -Djava.library.path in "mapred.child.java.opts".