Fixed Issues in Apache Oozie

Review the list of Oozie issues that are resolved in Cloudera Runtime 7.1.7 SP1.

CDPD-33993: Oozie will not turn to HDFS NameNode to "resolve" the share lib's file entries one by one before starts the Yarn application. If somehow this causes fault then this functionality can be turned off via a Cloudera Manager Safety Valve: oozie.classpathutils.resolve=true

This issue is now resolved.

CDPD-28768: Fork node splits one path of execution into multiple concurrent paths of execution and the join node waits until every concurrent execution path of a previous fork node arrives to it. Given a scenario, when one of the paths [action] fails for some exotic reason - for example with an EL Error - then the workflow job itself will fail as well, however the other actions running parallelly under the same workflow job will stuck in RUNNING state until they are purged, which can lead to Oozie slow-down in extreme cases.

This issue is now resolved.

CDPD-30045: Oozie's ZooKeeper related codebase now has extra trace level logging entries so in case of any ZooKeeper related issues these can be enabled. Affected classes: * org.apache.oozie.command.XCommand * org.apache.oozie.service.ZKLocksService

This issue is now resolved.

CDPD-30584: The Oozie client will display the full stacktrace in case it fails to connect to the Oozie server.

This issue is now resolved.

CDPD-24942: The Oozie client now has a --insecure option which behaves like the curl command's --insecure parameter. With this there's no need to specify the -Djavax.net.ssl.trustStore and -Djavax.net.ssl.trustStorePassword parameters when SSL is enabled in Oozie. The connection will still be encrypted, but the Oozie client will not validate the certification of the Oozie server.

This issue is now resolved.

CDPD-26335: Oozie did not accept a JDBC url if it contained special characters (e.g.: comma or curly brackets). This is fixed now so Oozie should accept special urls, for example a MySQL HA JDBC url where you typically use comma(s).

This issue is now resolved.

CDPD-30487: The Yarn application launched by Oozie creates a file for storing action related information which will be read by the Oozie server. In case the Yarn application is able to create this file, but won't be able to put the necessary data into it and so the file remains empty, the Oozie server will fail to parse this file. This error is now fixed.

This issue is now resolved.

CDPD-28080: Oozie web UI should not serve image from http://extjs.com/s.gif.

This issue is now resolved.

CDPD-30426: The oozie-default.xml had a default value for controlling the JPA retry wait time. The name of the property in the oozie-default.xml was: "oozie.service.JPAService.retry.maximum-wait-time.ms" however the Oozie server was looking for a property named "oozie.service.JPAService.maximum-wait-time.ms". This is now fixed and the oozie-default.xml and the Oozie server are now in sync. In case somebody already put an override as a safety-valve with a name "oozie.service.JPAService.maximum-wait-time.ms", then Oozie will prefer that.

This issue is now resolved.

CDPD-27661: There is a new property named "oozie.ui.enabled" users can set for Oozie with a value true of false. By default it's set to true. When set to false, the Oozie UI will be complete disabled, the Oozie server will not even expose the UI resources, hence this can be a workaround for the JQuery vulnerabilities.

This issue is now resolved.