[
https://issues.apache.org/jira/browse/YARN-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349305#comment-16349305
]
Jim Brennan commented on YARN-7677:
-----------------------------------
I have tested a version of the patch where I write out the whitelisted
variables first, and it does work for my test cases. But looking at the
launch_container.sh that is produced, the order of other variables is not the
same as launch_container.sh from before my changes. Since the whitelisted
variables are not added to the environment hash map, the order of traversal is
different. I'm not comfortable with putting this change in as-is, because while
the ordering differences I'm seeing are not a problem in my test cases, there
is no guarantee that others would not run into problems due to this change.
I discussed this with [~jlowe], and he pointed me at YARN-5714. I think we need
to address that problem before putting this change in.
> Docker image cannot set HADOOP_CONF_DIR
> ---------------------------------------
>
> Key: YARN-7677
> URL: https://issues.apache.org/jira/browse/YARN-7677
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Eric Badger
> Assignee: Jim Brennan
> Priority: Major
> Attachments: YARN-7677.001.patch, YARN-7677.002.patch
>
>
> Currently, {{HADOOP_CONF_DIR}} is being put into the task environment whether
> it's set by the user or not. It completely bypasses the whitelist and so
> there is no way for a task to not have {{HADOOP_CONF_DIR}} set. This causes
> problems in the Docker use case where Docker containers will set up their own
> environment and have their own {{HADOOP_CONF_DIR}} preset in the image
> itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
