Oozie
  1. Oozie
  2. OOZIE-23

Add configuration to set Oozie runtime directory

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.2.0, 3.3.0, 3.3.2
    • Fix Version/s: None
    • Component/s: core

      Description

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Yu Li
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development