bdacheckcluster reports "ERROR: <HOSTID> is in bad health" After BDA Node 3 or 4 Migration when the Node is Down and Decommissioned
(Doc ID 2041469.1)
Last updated on DECEMBER 04, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.2.0 and later
Running the cluster verifications with bdacheckcluster after migrating node 3 or 4 when the node is down and decommissioned reports "ERROR: <HOSTID> is in bad health". The yarn service may be reported in either "good", "concerning", or "bad" health.
For example after node migration bdacheckcluster may look like:
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