My Oracle Support Banner

Recovery for a Failed Standby NameNode that will not Restart on Oracle Big Data Appliance V2.3.1 and higher (Doc ID 1632817.1)

Last updated on MAY 30, 2021

Applies to:

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


Detail the steps to perform NameNode recovery due to a failure of a standby NameNode to restart.

The specific scenario addressed is when one NameNode remains Active but the Standby won't come up.   For example:


On BDA with automatic failover the expectation is that the Standby should become Active without intervention. If necessary the Standby can be made Active via the "Manual Failover" option in CM, or via the "Manual Failover - Force Failover" option in CM.


 Oracle Big Data Appliance (BDA) Administrators.


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
 NameNode Recovery from Failure of a Standby NameNode that will not Restart
 Overview of Steps for  NameNode Recovery when the Standby will not Restart - Active NameNode Functioning
 Preliminary Steps
 Backup Directories on NameNode where Recovery will Run
 NameNode Configuration Directory
 Navigator Required Updates to Current NameNode Configuration
 Perform Bootstrap
 Output from namenode -bootstrapStandby
 Start Bootstrapped NameNode in Cloudera Manager
 Starting up Other Services in Cloudera Manager
 Post Bootstrap Steps

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