Fixed Issues in Apache Oozie

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

CDPD-27541: In case Yarn resource manager is in HA and the resource manager for an Oozie action was specified with an alias then Oozie failed to obtain the actual Yarn RM principal because it could not resolve the hostname for the alias. This did not cause an issue if there were no auth-to-local rules as Oozie did a fallback to use the short name from the principal template. For example it extracted "yarn" from "yarn/_HOST@ROOT.HWX.SITE". However when there are auth-to-local rules then Yarn could not map the short name. This was fixed by Oozie handling the case when Yarn is in HA and/or a resource manager address alias is used.

This issue is resolved.

CDPD-26692: The Oozie purge process for bundles is creating orphan coordinators. When purging bundle jobs and bundle actions, it does not always purge coordinator jobs, etc. This causes orphaned coordinators, meaning neither they nor their children will ever be purged due to the purge logic. Hence the purge logic was modified to only purge bundles and coordinators if all of their children (Workflows) can be purged.

This issue is resolved.

CDPD-25982: Fixing a regression introduced in CDPD-21870 where we fixed an issues where Oozie always used the unix user and not the Kerberos user. However this fix did not take the Kerberos name rules into consideration which is now fixed in scope of this ticket.

This issue is resolved.

OPSAPS-59215: Oozie fails to start with JNI Group Mapping in CDP.

Oozie will now use the Hadoop native libraries when JNI group mapping is enabled. This issue is resolved.

CDPD-28593: Oozie fails to start when Callback Servlet Authentication is turned on.

When the Callback authentication was enabled Oozie failed to start up. This issue is resolved.