Support Questions

Find answers, ask questions, and share your expertise

unable to start namenode

avatar
Contributor

Israr_0-1728412487042.png

getting this error while starting id can't update anythind in adding snn or remove nn same shows anyone help me

1 ACCEPTED SOLUTION

avatar
Contributor

resolve this  by addin the conf in anothe nn, 

the conf are

1. NameNode Nameservice

2. Automatic failover tick

3. Quorum Journal name

View solution in original post

5 REPLIES 5

avatar
Super Collaborator

Hi @Israr,

It looks like you have enabled HA, but there is no secondary name node in your cluster. This complains about the configuration issue. Can you review your HDFS configs once?

Let us know if this helps.

avatar
Contributor
  1. what i have done after enabling i removed the standby namenode and now i added again on same node it's giving error.

avatar
Contributor

anybody has faced same issue and if you please let me know

avatar
Contributor

Israr_0-1728585513303.png

see this any body can help

 

avatar
Contributor

resolve this  by addin the conf in anothe nn, 

the conf are

1. NameNode Nameservice

2. Automatic failover tick

3. Quorum Journal name