[ https://issues.apache.org/jira/browse/IGNITE-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280410#comment-16280410 ]
ASF GitHub Bot commented on IGNITE-7080: ---------------------------------------- GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3161 IGNITE-7080 Check env variable names to only pass IGNITE_* to nodes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7080 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3161.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3161 ---- commit b3ececfd8a226da577fe2390142ac4ebc25b6e07 Author: Ilya Kasnacheev <ilya.kasnach...@gmail.com> Date: 2017-12-06T16:20:35Z IGNITE-7080 Check env variable names to only pass IGNITE_* to nodes. ---- > YARN fails to create containers if Bash functions exported in environment > ------------------------------------------------------------------------- > > Key: IGNITE-7080 > URL: https://issues.apache.org/jira/browse/IGNITE-7080 > Project: Ignite > Issue Type: Bug > Components: yarn > Affects Versions: 2.3 > Reporter: Ilya Kasnacheev > Assignee: Ilya Kasnacheev > Attachments: ignite-7080.patch > > > Ignite YARN collects all existing environment variables to pass them to > container, including variables with incorrect names, such as Bash functions, > which have extra characters at the end, and are ignored by most shells but > not the JVM. > When you tell Bash to export functions, it puts > BASH_FUNC_your_function_name%% variable into env. This is what is causing > problems because Ignite YARN picks this variable and tells Hadoop to pass it > to container, which leads to incorrectly written startup scrips. > Hadoop tries to sanitize env var values but not env var names. I think Ignite > should not try to pass all env vars to containers (it may contain sensitive > or master-specific vars!). We should only pass env vars that are relevant to > containers, such as IGNITE_* vars. > See > http://apache-ignite-users.70518.x6.nabble.com/Error-running-ignite-in-YARN-td18280.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)