My Oracle Support Banner

Mammoth Fails on Step 5: "Installing Hadoop Parcel and Upgrading CDH Cluster" During "Hadoop::Post_upgrade_features" (Doc ID 2488030.1)

Last updated on JANUARY 10, 2020

Applies to:

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

Symptoms

A Mammoth action fails on Step 5:"Installing Hadoop Parcel and Upgrading CDH Cluster" during "Hadoop::Post_upgrade_features" as below.  The example here is based on a Mammoth upgrade to 4.12, but the condition applies to any Mammoth action.

************************************
Error [17518]: (//<HOSTNAME>.<DOMAIN>//Stage[post]/Hadoop::Post_upgrade_features/Exec[exec_post_upgrade_features]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/post_upgrade_features.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/post_upgrade_features.out returned 1 instead of one of [0]
************************************

The file: /opt/oracle/BDAMammoth/bdaconfig/tmp/post_upgrade_features.out from node bdanode0x shows output like:

Configure Hive Metastore and Sentry HA
API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<cluster-name>_services_<##>.out
API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<cluster_name>_services_hive_roleConfigGroups_hive-HIVEMETASTORE-BASE_config_<##>.out
DEBUG - generate missing credentials
API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/cm_commands_generateCredentials.out
Command ID is 190378
...
Command 190387 finished after 5 seconds
Operation completed successfully
DEBUG - verify all Hive Metastore instances are running, start each oneif stopped
API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<cluster_name>_services_hive_roles_<##>.out
API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<cluster_name>_services_<##>.out
DEBUG - if ther are stale services after deploying Hive Metastore client configuration restart them
Number of stale services 1

API Version used is v19
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_<cluster_name>_commands_rollingRestart.out
Command ID is 190388

Command 190388 finished after 5 seconds
Operation failed
Result Message is: "There is already a pending command on this entity.",

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.