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 FEBRUARY 05, 2020
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:
The Active NN fails
The Standby becomes Active (either automatically, or via manual intervention in Cloudera Manager(CM), or via the manual "force" option in CM)
But the other NN (the previously Active one) is down, and can not be restarted in CM
Active stays up but the Standby goes down and can not be brought up in CM.
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!