My Oracle Support Banner

BDA Node Migration/Server Resilency Commands fail at Step 11 Due to Configured HBase Role - Node Can Not be Decommissioned (Doc ID 1957110.1)

Last updated on DECEMBER 09, 2019

Applies to:

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

Symptoms

NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

Node migration or other server resiliency command fails at step 11 with:

Error [6499]: (//bdanode03.example.com//Stage[main]/Hadoop::Startsvc2/Exec[setup_scm]/returns) change from notrun to 0 failed\
: /opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm.sh &>
/opt/oracle/BDAMammoth/bdaconfig/tmp/setupscm_1418253169.out returned 1 instead of one of [0]


1. From Cloudera Manager (CM) > All Recent Commands, Hosts Decommission is failing with:

Command 'DecommissionWithWait' failed for service 'hbase'

For example:



2. Drilling down into Child Commands shows for HBase:

Decommission (Graceful Stop)
Failed to perform decommission

For example:



3. Drilling down into the Command Details for the Decommission (Graceful Stop) shows:

Decommision worker roles on bdanode0x
Command Decommission (Graceful Stop) is not currently available for execution.

For example:



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
References


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