— Oozie does not work seamlessly with ResourceManger HA
Oozie workflows are not recovered on ResourceManager failover when ResourceManager HA is enabled. Further, users can not specify the clusterId for JobTracker to work against either ResourceManager.
Workaround: On non-secure clusters, users are required to specify either of the ResourceManagers' host:port. For secure clusters, users are required to specify the Active ResourceManger's host:port.
— When using Oozie HA with security enabled, some znodes have world ACLs
Oozie High Availability with security enabled will still work, but a malicious user or program can alter znodes used by Oozie for locking, possibly causing Oozie to be unable to finish processing certain jobs.
— Oozie and Sqoop 2 may need additional configuration to work with YARN
In CDH 5, MRv2 (YARN) MapReduce 2.0 is recommended over the Hadoop 0.20-based MRv1. The default configuration may not reflect this in Oozie and Sqoop 2 in CDH 5 Beta 2, however, unless you are using Cloudera Manager.
Workaround: Check the value of CATALINA_BASE in /etc/oozie/conf/oozie-env.sh (if you are running an Oozie server) and /etc/default/sqoop2-server (if you are using a Sqoop 2 server). You should also ensure that CATALINA_BASE is correctly set in your environment if you are invoking /usr/bin/sqoop2-server directly instead of using the service init scripts. For Oozie, CATALINA_BASE should be set to /usr/lib/oozie/oozie-server for YARN, or /usr/lib/oozie/oozie-server-0.20 for MRv1. For Sqoop 2, CATALINA_BASE should be set to /usr/lib/sqoop2/sqoop-server for YARN, or /usr/lib/sqoop2/sqoop-server-0.20 on MRv1.
— Oozie can't submit jobs to a secure MRv2 cluster if the Job History Server is down
After trying to submit the job (by default, three times), Oozie will SUSPEND the workflow automatically.
Workaround:When you bring up the Job History Server, use the resume command to tell Oozie to continue the workflow from where it left off.
— An Oozie server works either with a Hadoop MRv1 cluster or a Hadoop YARN cluster, not both
Anticipated Resolution: None planned
Workaround: Use two different Oozie servers
When you use the Hive action with Hive Server 2, Oozie won't collect or print out the Hadoop Job IDs of any jobs launched by Hive Server 2
Workaround: You can get the Hadoop IDs from the JobTracker.