Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
Solved Go to solution

unable to start namenode

Labels:
avatar
author-rank Israr
Contributor

Created on ‎10-08-2024 11:36 AM - last edited on ‎04-20-2026 11:25 PM by Community Manager Community Manager

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

3,096 Views
0 Kudos
1 ACCEPTED SOLUTION

avatar
author-rank Israr
Contributor

Created ‎10-10-2024 01:38 PM

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

3,000 Views
5 REPLIES 5

avatar
author-rank tj2007 author-rank
Super Collaborator

Created ‎10-08-2024 09:12 PM

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.

3,075 Views

avatar
author-rank Israr
Contributor

Created ‎10-09-2024 07:13 AM

  1. what i have done after enabling i removed the standby namenode and now i added again on same node it's giving error.
3,057 Views
0 Kudos

avatar
author-rank Israr
Contributor

Created ‎10-09-2024 07:14 AM

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

3,057 Views
0 Kudos

avatar
author-rank Israr
Contributor

Created ‎10-10-2024 11:38 AM

Israr_0-1728585513303.png

see this any body can help

 

3,010 Views

avatar
author-rank Israr
Contributor

Created ‎10-10-2024 01:38 PM

resolve this  by addin the conf in anothe nn, 

the conf are

1. NameNode Nameservice

2. Automatic failover tick

3. Quorum Journal name

3,001 Views
Announcements
Community Announcements
Community Upgrade Announcement
What's New @ Cloudera
Announcing Cloudera Flow Management Operator for Kubernetes ...
What's New @ Cloudera
Announcing Cloudera Streams Messaging Operator for Kubernete...
Community Announcements
July 2026 Community Highlights
Community Announcements
June 2026 Community Highlights
View More Announcements