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

Community Articles

Find and share helpful community-sourced technical articles.
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!

How to force Namenode failover in HA

Labels (1)
Labels:
avatar
author-rank ahallam
Expert Contributor

Created on ‎08-07-2017 10:02 AM

If you would like NN1 to be active namenode, you can do it by stopping ZKFC of NN2 via ambari.

After ~10 sec the failover should happend the the other NN become the active

2,505 Views
0 Kudos
Comments

Re: How to force Namenode failover in HA

avatar
author-rank abhijth8
New Member

Created on ‎08-09-2017 06:18 PM

Doing this process may lead to bad things in a production cluster. The right way would be.

hdfs haadmin -failover nn1 nn2

The NN UI shows the service tags

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
Version history
Last update:
‎08-07-2017 10:02 AM
Updated by:
Expert Contributor
Contributors