Jason Lowe updated YARN-7677:
    Fix Version/s:     (was: 3.1.0)

I reverted this from trunk and branch-3.1.  While the breakage is definitely 
triggered by this JIRA, I actually think the root cause is the same problem 
described in YARN-5714.

The only explicit ordering change done by this JIRA is to place inherited NM 
whitelisted variables before variables in the container launch context.  
Looking at Rohith's configs, neither CLASSPATH nor HADOOP_MAPRED_HOME are in 
the NM whitelist variables.  Therefore I think this JIRA ended up inadvertently 
changing the iteration order of the user environment hashmap due to fewer 
variables being stored in that hashmap than before.

We're going to have to wait until YARN-5714 is fixed before this can go 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, 
> YARN-7677.003.patch, YARN-7677.004.patch, YARN-7677.005.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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to