[
https://issues.apache.org/jira/browse/MAPREDUCE-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli reopened MAPREDUCE-2748:
------------------------------------------------
Assignee: (was: Arun C Murthy)
I am reopening this ticket for tracking the effort to make the list of envs to
be configurable.
MAPREDUCE-2880 already fixed the code to pass correct values for essential
variables like HADOOP_COMMON_HOME from NM down to the containers. It will be
useful to have this configurable - like JAVA_HOME for containers separate from
the NM's JAVA_HOME, or may be extra envs that NM doesn't need to be set with.
Also another minor TODO is to verify that the streaming examples I commented
about above are working now.
> [MR-279] NM should pass a whitelisted environmental variables to the
> container
> -------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2748
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2748
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Fix For: 0.23.0
>
>
> This is similar to [MAPREDUCE-103] . We should pass a whitelisted set of
> environment variables from NM env to the container. By default, we should
> pass HADOOP_* variables. This can be a simple configuration key that
> NodeManager reads.
> Today, we already either pass the following correctly or assume that it works
> but doesn't
> - YARN_HOME: ContainerLaunch#writeLaunchEnv
> - HADOOP_CLIENT_OPTS: MapReduceChildJVM#setVMEnv
> - JAVA_HOME: TaskAttemptImpl#createContainerLaunchContext - Works by
> shell-expansion.
> - LD_LIBRARY_PATH: Assumed to work via shell-expansion but doesn't.
--
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
