[
https://issues.apache.org/jira/browse/YARN-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173190#comment-16173190
]
Shane Kumpf commented on YARN-7034:
-----------------------------------
Thanks for addressing my comments [[email protected]]. I tested all
three of the latest patches and the changes look good to me. +1 (non-binding).
> 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,
> YARN-7034.002.patch, YARN-7034.003.patch, YARN-7034.004.patch,
> YARN-7034.005.patch, YARN-7034.006.patch, YARN-7034.branch-2.000.patch,
> YARN-7034.branch-2.004.patch, YARN-7034.branch-2.005.patch,
> YARN-7034.branch-2.006.patch, YARN-7034.branch-2.8.000.patch,
> YARN-7034.branch-2.8.004.patch, YARN-7034.branch-2.8.005.patch,
> YARN-7034.branch-2.8.006.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]
