[
https://issues.apache.org/jira/browse/OOZIE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated OOZIE-23:
-----------------------
Component/s: core
Environment: (was: RHEL 64 bit vms, distributed Hadoop 0.20.2
with JobTracker and TaskTracker/DataNode on different nodes)
Affects Version/s: 3.2.0
3.3.0
3.3.2
Remaining Estimate: (was: 168h)
Original Estimate: (was: 168h)
> Add configuration to set the Oozie temporary runtime directory
> --------------------------------------------------------------
>
> Key: OOZIE-23
> URL: https://issues.apache.org/jira/browse/OOZIE-23
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.2.0, 3.3.0, 3.3.2
> Reporter: Yu Li
> Labels: configuration,, runtime
>
> I'm trying to make oozie work with NFS rather than HDFS, but find it hard to
> set the Oozie temporary runtime directory into the NFS mount point. I'm using
> the java api and lauching a simple oozie job through OozieClient, the code is
> like below:
> OozieClient wc = new OozieClient("http://dev001:8080/oozie";);
> Properties conf = wc.createConfiguration();
> conf.setProperty(OozieClient.APP_PATH, "/mnt/nfs/my-wf-app");
> conf.setProperty("jobTracker", "dev001:9001");
> conf.setProperty("inputDir", "/mnt/nfs/usr/tester/inputdir");
> conf.setProperty("outputDir", "/mnt/nfs/usr/tester/outputdir");
> String jobId = wc.run(conf);
> System.out.println("Workflow job submitted");
> In my environment the JT is on dev001 and TT is on dev002, and with the above
> codes, the Oozie temporary runtime directory is generated under
> "/home/tester/oozie-test" on dev001, so the job failed because there's no
> such directory on dev002.
> If only I could set the temporary dicectory into some dir under "/mnt/nfs"
> the problem could be resolved, but I've looked through the OozieClient
> javadoc, and there seemed to be no property to set the temporary runtime
> directory. I also looked through the oozie-default.xml, failed to find such
> setting, either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
