Step 4: Post Software Upgrade

After you upgrade the Oozie software packages, you may need to complete the following additional steps:
  1. Add customized properties from the configuration files that you saved before the upgrade to the files in the new Oozie conf directory: /opt/mapr/oozie/oozie-<version>/conf/.
  2. For upgrades from Oozie 4.0.x to Oozie 4.2.0, run the following command to upgrade the database schema:
    # /opt/mapr/oozie/oozie-<version>/bin/ooziedb.sh upgrade -run
  3. When you upgrade the core MapR version on a cluster that already has Oozie installed, a packaging error results in Oozie building its WAR file with an incorrect version of maprfs.jar. To work around this issue, run the oozie-setup.sh script to rebuild the WAR file with the correct JARs:
    # sudo -u mapr maprcli node services -name oozie -action stop -nodes <nodelist>
    # sudo /opt/mapr/oozie/oozie-<version>/bin/oozie-setup.sh -hadoop <version> /opt/mapr/hadoop/hadoop-<version>
  4. If your Oozie installation is configured to use a MySQL or Oracle database, complete the following steps:
    1. Copy the JDBC driver jar file to the following directory:
      /opt/mapr/oozie/oozie-<oozie version>/libext
    2. Run the following command to upgrade the database schema:
      # /opt/mapr/oozie/oozie-<version>/bin/ooziedb.sh upgrade -run
      Note: This step is not required if you ran this command in step 2.
    3. Execute the oozie-setup.sh script to add the driver jar file to the Oozie WAR file:
      For Oozie 4.1-1506 or lower and Oozie 4.2.0 -1510 or lower:
      # sudo /opt/mapr/oozie/oozie-<version>/bin/oozie-setup.sh -hadoop <version> /opt/mapr/hadoop/hadoop-<version> prepare-war -extjs /tmp/ext-2.2.zip
      As of Oozie 4.1.0-1601 and Oozie 4.2.0-1601:
      # sudo /opt/mapr/oozie/oozie-<version>/bin/oozie-setup.sh -hadoop <version> /opt/mapr/hadoop/hadoop-<version>
  5. Verify the status of the Oozie service and start it manually if necessary:
    # service mapr-oozie status
    # sudo -u mapr maprcli node services -name oozie -action start -nodes <nodelist>
  6. Start any Oozie coordinators that you stopped before the upgrade.
  7. As of Oozie 4.1.0-1601 and Oozie 4.2.0-1601, if the oozie.service.WorkflowAppService.system.libpath property in oozie-site.xml does not use the default value (/oozie/share/), you must run perform the following steps to update the shared libraries:
    1. Based on the cluster MapReduce mode, run one of the following commands to copy the new Oozie shared libraries to MapR-FS:
      Cluster MapReduce Mode Command
      YARN
      sudo -u mapr {OOZIE_HOME}/bin/oozie-setup.sh sharelib create -fs maprfs:/// -locallib /opt/mapr/oozie/oozie-<version>/share2
      Classic
      sudo -u mapr {OOZIE_HOME}/bin/oozie-setup.sh sharelib create -fs maprfs:/// -locallib /opt/mapr/oozie/oozie-<version>/share1
    2. Run the following command to update the Oozie classpath with the new shared libraries:
      sudo -u mapr {OOZIE_HOME}/bin/oozie admin -sharelibupdate