Oracle Big Data Appliance "mammoth -p" Upgrade to V2.4 Release Fails when Impala Version Prior to 1.2 Managed by CM is being Upgraded (Doc ID 1610766.1)

Last updated on OCTOBER 11, 2016

Applies to:

Big Data Appliance Integrated Software - Version 2.1.1 to 2.4.0 [Release 2.1 to 2.4]
Linux x86-64

Symptoms

 If Impala version prior to 1.2 managed by Cloudera Manager(CM) is installed on BDA Cluster being upgraded then upgrade('mammoth -p') fails with an error like below:

INFO: Configuring the Hive Service. This will take some time ...
INFO: Puppet script successfully sent to node <node01>
..............
ERROR: Puppet agent run on node <node04> had errors. List of errors follows

************************************
Error [9635]: (//<node03>//Stage[main]/Hive::Setuphive/Exec[enable_hive_autocreate_schema]/returns) change from notrun to 0 failed:

/opt/oracle/BDAMammoth/bdaconfig/tmp/enablehiveschema.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/enablehiveschema_1388106937.out returned 1 instead of one of [0] at

/opt/oracle/BDAMammoth/puppet/modules/hive/manifests/setuphive.pp:139
************************************

Note:- 1388106937 in enablehiveschema_1388106937.out refers to a random identifier.

On <node03> reviewing enablehiveschema_<random-id>.out states the failure is caused while starting Impala service:

# more /opt/oracle/BDAMammoth/bdaconfig/tmp/enablehiveschema_1388106937.out
API Version used is v5
Succeeded. Output in : /opt/oracle/BDAMammoth/bdaconfig/tmp/clusters_scaj_comman
ds_start.out
Command ID is 478
.......................
Command 478 finished after 120 seconds
Operation failed
Result Message is:   "Command 'Start' failed for service 'impala1'"

When upgrading from 2.3.* to 2.4 release a generic error message will be thrown like below during 'Step 7: Restarting Hadoop Services'

************************************
Error [8240]: (//scaj22bda04.us.oracle.com//Stage[main]/Hadoop::Startcloudera/Exec[start_cloudera_services]/returns) change from notrun to 0

failed: Command exceeded timeout at /opt/oracle/BDAMammoth/puppet/modules/hadoop/manifests/startcloudera.pp:23
************************************

Trying to manually start Impala service from Cloudera Manager(CM) fails with

Command failed to run because service impala1 has invalid configuration. Review and correct its configuration. First error: Service impala1 has 0 Impala Catalog Server Daemons. Impala requires at least 1 Impala Catalog Server Daemon.

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