[jira] [Updated] (OOZIE-1958) address duplication of env variables in oozie.launcher.yarn.app.mapreduce.am.env when running with uber mode

["Rohini Palaniswamy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohini Palaniswamy updated OOZIE-1958:
--------------------------------------

    Fix Version/s: 4.1.0

  Marking this for 4.1 as this is important for hadoop 2.x

> address duplication of env variables in oozie.launcher.yarn.app.mapreduce.am.env when running with uber mode
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1958
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1958
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Ryota Egashira
>            Assignee: Ryota Egashira
>             Fix For: 4.1.0
>
>
> Hadoop 2.X has the weird behavior to translate yarn.app.mapreduce.am.env,
> JAVA_HOME=/home/gs/java/jdk64/current,JAVA_HOME=/home/gs/java/jdk64/current 
> to
> JAVA_HOME=/home/gs/java/jdk64/current:JAVA_HOME=/home/gs/java/jdk64/current
> due to this, some of env variables are not taken in effect properly.
> this problem happens when running launcher with uber mode in Hadoop 2.X, 
> since oozie copies mapreduce.map.env to yarn.app.mapreduce.am.env, like following case
>   
> {code}
> <property>
>       <name>oozie.launcher.mapreduce.map.env</name>
>       <value>JAVA_HOME=/home/gs/java/jdk64/current</value>
> </property>
> <property>
>       <name>oozie.launcher.yarn.app.mapreduce.am.env</name>
>       <value>JAVA_HOME=/home/gs/java/jdk64/current</value>
> </property>
> {code}
> this patch is to do 
>    1) Deduplication before appending map.env to am.env
>    2) If there is a conflict, turn of uber mode AM. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)