My Oracle Support Banner

Migrating a Failed Mammoth Node with "bdacli admin_cluster migrate <ORIGINAL_MAMMOTH_HOSTNAME>" on BDA 5.2 Fails in StartHadoopServices with "NameNode is not formatted." (Doc ID 2945613.1)

Last updated on MAY 02, 2023

Applies to:

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

Symptoms

NOTE: In the examples 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.

Migrating a failed Mammoth node to another host on BDA 5.2 using the command below fails in the StartHadoopServices step. Note the command is run on the node which will become the new Mammoth node.

Note this issue is different from that in: Migrating a Failed Mammoth Node with "bdacli admin_cluster migrate <ORIGINAL_MAMMOTH_HOSTNAME>" on BDA 5.2 Fails in StartHadoopServices with "Failed to bootstrap Standby NameNode" (Doc ID 2945767.1).  However both issues can occur in the same Mammoth node migration.

Changes

 

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
Changes
Cause
Solution
References


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