My Oracle Support Banner

"bdacli admin_cluster decommission bdanode0x" is Successful But the Node is Not Decommissioned (Doc ID 2393563.1)

Last updated on FEBRUARY 06, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.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. 

The symptoms are:

1. "bdacli admin_cluster decommission bdanode0x" completes successfully.

2. The QUARANTINED lists in /opt/oracle/bda/install/state/config.json correctly report the node as being quarantined.

If for example Node 6, i.e. bdanode06 is decommisioned /opt/oracle/bda/install/state/config.json correctly shows:

a) The "QUARANTINED_POSNS" is 5.

"QUARANTINED_POSNS" :
[
"5"
],

Note: The QUARANTINE_POSN is zero based.

b) The "QUARANTINED_HOSTS" is bdanode06.

"QUARANTINED_HOSTS" :
[
"bdanode06"
],

3. However the node is not decommissioned because:

a) In CM, the Node <X> is not decommissioned.
b) In CM the DN for Node <X> is not stopped.
c) In CM the NM for Node <X> is not stopped.

 

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.