After a Successful Mammoth Expansion the Oozie Service is in Bad Health with Cloudera Manager Reporting that the Oozie Server Build Version and the Oozie Server Shared Library Version Do Not Match.

(Doc ID 2369142.1)

Last updated on MARCH 04, 2018

Applies to:

Big Data Appliance Integrated Software - Version 4.11 and later
Linux x86-64

Symptoms

1. After a successful Mammoth expansion the Oozie service is in bad health with Cloudera Manager(CM) reporting that the Oozie server build version and the Oozie server shared library version do not match.

For example a warning like below when doing a BDA v4.11/CDH 5.13.1 Mammoth expansion is raised:

The Oozie Server build version(4.1.0-cdh5.9.0) and the Oozie Server shared library version(4.1.0-cdh5.13.1) do not match.

2. Further checking Cloudera Manager: Hosts > Parcels shows that the CDH5 parcel for an older parcel version is Distributed,Activated and the new/correct parcel version has a status of "Upgrade Cluster". This indicates that the new/correct CDH5 parcel was not upgraded.

For example during a BDA v4.11/CDH 5.13.1 Mammoth expansion Hosts > Parcels shows:

3. Running the Host Inspector in CM: Hosts > Inspect All Hosts > Show Inspector Results, shows the CDH parcel for all CDH components at the lower/incorrect version.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms