[OOZIE-1794] java-opts and java-opt in the Java action don't always work properly in YARN

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 11/Apr/14 22:52
• Updated: 09/Dec/14 00:45
• Resolved: 24/Apr/14 19:09

Description

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.