Migrating a Failed Mammoth Node with "bdacli admin_cluster migrate <ORIGINAL_MAMMOTH_HOSTNAME>" on BDA 5.2 Fails in Step 1 PreinstallChecks because the One Remaining NameNode Continuously Goes into Safe Mode
(Doc ID 2945590.1)
Last updated on MAY 02, 2023
Applies to:Big Data Appliance Integrated Software - Version 5.2.0 and later
Migrating a failed Mammoth node to another host on BDA 5.2 using the command below fails in Step 1 PreinstallChecks. Note the command is run on the node which will become the new Mammoth node.
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