Known Issues in Apache Oozie

Learn about the known issues in Oozie, the impact or changes to the functionality, and the workaround.

CDPD-29302: The Atlas lineage information is missing in case of HWC JDBC write.

None

CDPD-29297: HWC + Oozie issue: Cannot create PoolableConnectionFactory

Currently only Spark cluster mode is supported in the Oozie Spark Action with Hive Warehouse Connector (HWC).

Use Spark action in cluster mode.

<spark xmlns="uri:oozie:spark-action:1.0">
                        ...
                        <mode>cluster</mode>
                        ...
                        </spark>

CDPD-26975: Using the ABFS / S3A connectors in an Oozie workflow where the operations are "secured" may trigger an IllegalArgumentException with the error message java.net.URISyntaxException: Relative path in absolute URI.

Set the following XML configuration in the Datahub cluster's Cloudera Manager:

1. In the Cloudera Manager Admin Console, go to the Oozie service.
2. Click the Configuration tab.
3. In the Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml field, set the following:
   Set the following if you are using Amazon S3:

    <property>
                                       <name>oozie.service.HadoopAccessorService.fs.s3a</name>
                                       <value>fs.s3a.buffer.dir=/tmp/s3a</value>
                                       </property>

   Set the following if you are using ABFS:

   <property>
                                               <name>oozie.service.HadoopAccessorService.fs.abfs</name>
                                               <value>fs.azure.buffer.dir=/tmp/abfs</value>
                                               </property>
                                               <property>
                                               <name>oozie.service.HadoopAccessorService.fs.abfss</name>
                                               <value>fs.azure.buffer.dir=/tmp/abfss</value>
                                               </property>

4. Enter a Reason for change, and then click Save Change to commit the changes.
5. Restart the Oozie service.

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.

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.

CDPD-5340: The resourceManager property defined in an Oozie workflow might not work properly if the workflow is submitted through Knox proxy.

An Oozie workflow defined to use the resourceManager property might not work as expected in situations when the workflow is submitted through Knox proxy.

Define the jobTracker property with the same value as that of the resourceManager property.

Unsupported Feature

The following Oozie features are currently not supported in Cloudera Data Platform:

• Non-support for Pig action (CDPD-1070)
• Conditional coordinator input logic

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.

BUG-123856: Upgrade fails while configuring Oozie server.

None