Known Issues in Apache Oozie

This topic describes known issues and unsupported features for using Oozie in this release of Cloudera Runtime.

CDH-14623: Oozie jobs fail (gracefully) on secure YARN clusters when JobHistory server is down

If the JobHistory server is down on a YARN (MRv2) cluster, Oozie attempts to submit a job, by default, three times. If the job fails, Oozie automatically puts the workflow in a SUSPEND state.

Workaround: When the JobHistory server is running again, use the resume command to inform Oozie to continue the workflow from the point at which it left off.

Oozie works with MapReduce or YARN, but not both

The Oozie server works with a MapReduce (MRv1) cluster or a YARN (MRv2) cluster, but not both at the same time.

Workaround: Use two different Oozie servers.

CDPD-1773: Oozie throws an error when submitting a YARN application on a cluster that uses Amazon S3 as the secondary filesystem

On a cluster that uses Amazon S3 as a secondary filesystem, an ActionExecutorException is thrown when Oozie tries to submit a YARN application.

Workaround: Update workflow.xml with information about the following two properties:

<property>
             <name>oozie.launcher.fs.s3a.fast.upload.buffer</name>
             <value>bytebuffer</value>
         </property>
         <property>
              <name>oozie.launcher.fs.s3a.impl.disable.cache</name>
              <value>true</value>
         </property>

Unsupported Feature

The following Oozie feature is currently not supported in Cloudera Data Platform:

• Non-support for Pig action (CDPD-1070)

Cloudera does not support using Derby database with Oozie. You can use it for testing or debugging purposes, but Cloudera does not recommend using it in production environments. This could cause failures while upgrading from CDH to CDP.