Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1794

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

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 4.1.0
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

        1. OOZIE-1794.patch
          21 kB
          Robert Kanter
        2. OOZIE-1794.patch
          21 kB
          Robert Kanter
        3. OOZIE-1794.patch
          14 kB
          Robert Kanter
        4. OOZIE-1794.patch
          7 kB
          Robert Kanter

          Activity

            People

            • Assignee:
              rkanter Robert Kanter
              Reporter:
              rkanter Robert Kanter
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: