You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/02/12 19:02:12 UTC
[jira] [Resolved] (OOZIE-2066)
oozie.launcher.mapreduce.task.classpath.user.precedence is not respected
[ https://issues.apache.org/jira/browse/OOZIE-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter resolved OOZIE-2066.
----------------------------------
Resolution: Not a Problem
> oozie.launcher.mapreduce.task.classpath.user.precedence is not respected
> ------------------------------------------------------------------------
>
> Key: OOZIE-2066
> URL: https://issues.apache.org/jira/browse/OOZIE-2066
> Project: Oozie
> Issue Type: Bug
> Environment: yarn
> Reporter: Tim Robertson
> Priority: Critical
> Attachments: test-wf.zip
>
>
> 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.
> {code:xml}
> <property>
> <name>oozie.launcher.mapreduce.task.classpath.user.precedence</name>
> <value>true</value>
> </property>
> {code}
> When used in a Java action:
> {code:xml}
> <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>
> {code}
> However, it is not...
> There is a workaround, by setting this on the task directly in the workflow:
> {code:xml}
> <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>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)