[
https://issues.apache.org/jira/browse/YARN-10664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295589#comment-17295589
]
Jim Brennan commented on YARN-10664:
------------------------------------
It would have to be an environment variable that contains a variable denoted
with the expansion characters, double squigglies. Looking through
{{santizeEnv()}}, I don't see anything that would potentially include those,
other than {{NM_ADMIN_USER_ENV}} itself. If someone was using those in an
{{NM_ADMIN_USER_ENV}}-defined variable, and depending on that not being
expanded, that would be a problem. But I don't think that is likely.
Looking back at the {{call()}} method, there might be a problem there. There
is code that adds {{KEYSTORE_PASSWORD_ENV_NAME}} to the environment. If it is
possible for that value to have those characters, that might cause an unwanted
expansion. Might need to move the setting of those truststore variables after
the call to {{expandEnvironment}}.
> Allow parameter expansion in NM_ADMIN_USER_ENV
> ----------------------------------------------
>
> Key: YARN-10664
> URL: https://issues.apache.org/jira/browse/YARN-10664
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: yarn
> Affects Versions: 2.10.1, 3.4.0
> Reporter: Jim Brennan
> Assignee: Jim Brennan
> Priority: Major
> Attachments: YARN-10664.001.patch, YARN-10664.002.patch,
> YARN-10664.003.patch
>
>
> Currently, {{YarnConfiguration.NM_ADMIN_USER_ENV}} does not do parameter
> expansion. That is, you cannot specify an environment variable such as
> {code}{{JAVA_HOME}}{code} and have it be expanded to {{$JAVA_HOME}} inside
> the container.
> We have a need for this in specifying different java gc options for java
> processing running inside yarn containers based on which version of java is
> being used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
