Mammoth 2.0.1 Fails at Step 12 with "Unsuccessful 'BootstrapStandbyNameNode"
Last updated on MARCH 23, 2014
Applies to:Big Data Appliance Integrated Software - Version 2.0.1 and later
Running mammoth to configure V2.0.1 fails at step 12 with an error like:
However the problem is not:
Mammoth 2.0.1 Fails at Step 12 with "Validation of directories of namenode (bda01node02) failed" (Doc ID 1522753.1)
Since the mammoth parameters file is up-to-date for V2.0.1 and does not contain an NFS_DIRECTORY entry.
Further investigation shows that in the timeframe just prior to the error above the Cloudera server log points to an error bootstrapping the standby name node. The file:
contains messaging indicating: "Unsuccessful 'BootstrapStandbyNameNode'"
<Date just before DateX above> WARN [CommandPusher:command.CommandHelpers@275] Failed to bootstrap Standby NameNode namenode (<server2>) See error message and logs for cause of failure. After addressing the cause of failure, press 'Retry'. Alternatively, revert the performed steps using the 'Disable High Availability' action and try 'Enable High Availability' again. Note that the contents of the shared edits directory and the Standby NameNode's name directories need to be deleted before trying again. If this is undesirable, perform the remaining steps manually using the commands available in 'Actions'.
<Date just before DateX above> INFO [...@scm-web-5:cmf.AuthenticationSuccessEventListener@23] Authentication success for user: admin
<Date just before DateX above> INFO [...@scm-web-5:config.CMURLEvaluator@67] Using <server3> as CM's hostname
<DateY> INFO [StaleEntityEviction:model.HeartbeatStore@107] Reaped 0 process heartbeats and 0 host heartbeats.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms