[
https://issues.apache.org/jira/browse/YARN-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144277#comment-16144277
]
Robert Kanter commented on YARN-7034:
-------------------------------------
We generally trust the yarn user, and the cluster admin who set up Yarn, so I
think it should be okay to add the {{yarn.nodemanager.admin-env}} list in. The
end user had no control over that config. If we don't allow the admin-env, we
may make things difficult for some setups if there is a legit reason to set an
env var - otherwise, the environment is always empty and no way to change that.
> DefaultLinuxContainerRuntime and DockerLinuxContainerRuntime sends client
> environment variables to container-executor
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-7034
> URL: https://issues.apache.org/jira/browse/YARN-7034
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Miklos Szegedi
> Assignee: Miklos Szegedi
> Priority: Critical
> Attachments: YARN-7034.000.patch, YARN-7034.001.patch
>
>
> This behavior is unnecessary since there is nothing that is used from the
> environment right now. One option is to whitelist these variables before
> passing them. Are there any known use cases for this to justify?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
