Known Issues in Oozie

Known issues and technical limitations for Oozie are addressed in Cloudera Runtime 7.3.3.

Known Issues identified in Cloudera Runtime 7.3.3

There are no new known issues identified in this release.

Known Issues identifed before Cloudera Runtime 7.3.3

CDPD-93327: Passwords may be printed in the atlas-application.properties file
7.3.3.0, 7.3.2 and its SPs and CHFs
The /etc/atlas/conf/atlas-application.properties file is a publically readable file, and it may contain the Java trust store password. This file is read by the Oozie server and is propagated to the running actions. This allows the trust store password in the /etc/atlas/conf/atlas-application.properties file to be printed in the Oozie Launcher AM's (Yarn application) console logs, and the whole atlas-application.properties file is copied into the Oozie Launcher AM's (Yarn application) local directory.
None
Oozie jobs fail (gracefully) on secure YARN clusters when JobHistory server is down
7.3.3.0, 7.3.2.0 and its SPs and CHFs

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.