Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Enable Namenode Ha Fails in Inetialize Namenode HA metadata in HDP 3.0.1

Highlighted

Enable Namenode Ha Fails in Inetialize Namenode HA metadata in HDP 3.0.1

Super Collaborator

Hello Team,

Enable Namenode HA set up went upto Namenode HA Metadata step.

After ran below command in second nn2 host

hdfs namenode -bootstrapStandby in nn2 we have received the below error:

STARTUP_MSG: build = git@github.com:hortonworks/hadoop.git -r 2820e4d6fc7ec31ac42187083ed5933c823e9784; compiled by 'jenkins' on 2018-09-19T10:19Z STARTUP_MSG: java = 1.8.0_112 ************************************************************/ 18/11/19 12:56:51 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT] 18/11/19 12:56:51 INFO namenode.NameNode: createNameNode [-bootstrapStandby] 18/11/19 12:56:52 ERROR namenode.NameNode: Failed to start namenode. java.io.IOException: java.lang.IllegalStateException: Could not determine own NN ID in namespace 'o9cluster'. Please ensure that this node is one of the machines listed as an NN RPC address, or configure dfs.ha.namenode.id at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.run(BootstrapStandby.java:456) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1615) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1710) Caused by: java.lang.IllegalStateException: Could not determine own NN ID in namespace 'o9cluster'. Please ensure that this node is one of the machines listed as an NN RPC address, or configure dfs.ha.namenode.id at com.google

The above error looks like wrong configuration in custom hdfs-site.xml. we really not sure why ambari made wrong host-nn2 entry in hdfs-site.xml . we revert back to the original nn2 host entry for the below properties

dfs.namenode.http-address.o9cluster.nn2

dfs.namenode.https-address.o9cluster.nn2

dfs.namenode.rpc-address.o9cluster.nn2

still i am facing the same issue while running hdfs namenode -bootstrapStandby in nn2 server.

how to overcome this issue and proceed to further ??

Don't have an account?
Coming from Hortonworks? Activate your account here