[ https://issues.apache.org/jira/browse/OOZIE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter updated OOZIE-1794: --------------------------------- Attachment: OOZIE-1794.patch The new patch makes both properties always equal. I also added more detail about this behavior to the docs and updated the unit tests. > java-opts and java-opt in the Java action don't always work properly in YARN > ---------------------------------------------------------------------------- > > Key: OOZIE-1794 > URL: https://issues.apache.org/jira/browse/OOZIE-1794 > Project: Oozie > Issue Type: Bug > Affects Versions: trunk > Reporter: Robert Kanter > Assignee: Robert Kanter > Attachments: OOZIE-1794.patch, OOZIE-1794.patch, OOZIE-1794.patch > > > Currently, when you set {{<java-opts>}} or {{<java-opt>}} in the Java action, > it essentially appends these to {{mapred.child.java.opts}} in the launcher > job. > In YARN, this property is deprecated in favor or {{mapreduce.map.java.opts}} > and {{mapreduce.reduce.java.opts}}. And if > {{mapreduce.map/reduce.java.opts}} is set, {{mapred.child.java.opts}} will be > ignored. So in a YARN cluster where mapred-site.xml has > {{mapreduce.map.java.opts}} set to something, {{<java-opts>}} and > {{<java-opt>}} won't work at all. > We should have {{<java-opts>}} and {{<java-opt>}} append to both > {{mapred.child.java.opts}} and {{mapreduce.map.java.opts}}. -- This message was sent by Atlassian JIRA (v6.2#6252)