[
https://issues.apache.org/jira/browse/YARN-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612405#comment-15612405
]
Daniel Templeton commented on YARN-5771:
----------------------------------------
Sorry for restating the obvious. I missed the context of MAPREDUCE-6704.
I don't think that letting users control the whitelisting on a per-job basis is
the right answer. As far as I can tell, the problem we're trying to solve here
is that it should just work out of the box. The simplest and sanest answer,
IMO, is what you proposed on MAPREDUCE-6704: add {{HADOOP_MAPRED_HOME}} to
{{yarn.nodemanager.env-whitelist}} by default. I agree with [~aw] that users
aren't going to be offended by a little pollution if it means things just work.
> Provide option to send env to be whitelisted in ContainerLaunchContext
> -----------------------------------------------------------------------
>
> Key: YARN-5771
> URL: https://issues.apache.org/jira/browse/YARN-5771
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Attachments: container-whitelist-env-wip.patch
>
>
> As per current implementation ENV to be white listed for container launch is
> are configured as part of {{yarn.nodemanager.env-whitelist}}
> Specific to container we cannot specify additional ENV properties to be
> whitelisted. As part of this jira we are providing an option to provide
> additional whitelist ENV.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
