Robert Kanter created OOZIE-1794:
------------------------------------
Summary: 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
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)
