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

oozie.launcher.mapreduce.task.classpath.user.precedence is not respected

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Not A Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      yarn

      Description

      When using MR2, the user classpath precedence is not read from the job configuration.

      When submitting a job, the following configuration should result in the java action running with the user classpath before the Hadoop jars.

      <property>
        <name>oozie.launcher.mapreduce.task.classpath.user.precedence</name>
        <value>true</value>
      </property>
      

      When used in a Java action:

      <action name="run-test">
        <java>
          <job-tracker>c1n2.gbif.org:8032</job-tracker>
          <name-node>hdfs://c1n1.gbif.org:8020</name-node>
          <main-class>test.CPTest</main-class>
        </java>
        <ok to="end" />
        <error to="kill" />
      </action>
      

      However, it is not...

      There is a workaround, by setting this on the task directly in the workflow:

      <action name="run-test">
        <java>
          <job-tracker>c1n2.gbif.org:8032</job-tracker>
          <name-node>hdfs://c1n1.gbif.org:8020</name-node>
          <configuration>
            <property>
              <name>oozie.launcher.mapreduce.task.classpath.user.precedence</name>
              <value>true</value>
            </property>
          </configuration>
          <main-class>test.CPTest</main-class>
        </java>
        <ok to="end" />
        <error to="kill" />
      </action>
      

        Attachments

        1. test-wf.zip
          8 kB
          Tim Robertson

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              timrobertson100 Tim Robertson
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: