[
https://issues.apache.org/jira/browse/MAPREDUCE-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13136619#comment-13136619
]
Arun C Murthy commented on MAPREDUCE-3259:
------------------------------------------
Kihwal, sorry if I wasn't clear.
If the admins set mapreduce.admin.user.env such that LD_LIBRARY_PATH includes
paths for libhadoop.so and JNI-based user-groups mapping, what goes wrong?
mapreduce.admin.user.env is for cluster-level configs (libhadoop, user-groups
mapping etc.) and app-specific deps can go in mapreduce.(map,reduce).env. What
am I missing here?
> ContainerLocalizer should get the proper java.library.path from
> LinuxContainerExecutor
> --------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3259
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3259
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Blocker
> Fix For: 0.23.0, 0.24.0
>
> Attachments: mapreduce-3259.patch, mapreduce-3259.patch.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
