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]
Created 02-21-2017 06:53 AM
Does performing a:
hdfs haadmin -failover nn1 nn2
Ever a disruptive procedure? Suppose all services are up and running (zookeeper, zkfc, JN), it's my understanding that this should be a safe procedure and wouldn't cause jobs to fail, but wanted to know in what circumstances would this potentially be problematic.
Created 03-13-2017 08:45 PM
No, it is a non-disruptive procedure, provided that the cluster is healthy and is not under a heavy load. One of reasons to do so is for upgrading namenode, either software or hardware.
During a namenode failover, the jobs and clients application will be redirected from the old active namenode to the new active namenode. Of course, they have to wait until the new active namenode becomes ready so that they are slowed down. In this sense, we are better to perform the failover operation when the cluster is idea or under a small load.
Hope it helps.
Created 03-13-2017 08:45 PM
No, it is a non-disruptive procedure, provided that the cluster is healthy and is not under a heavy load. One of reasons to do so is for upgrading namenode, either software or hardware.
During a namenode failover, the jobs and clients application will be redirected from the old active namenode to the new active namenode. Of course, they have to wait until the new active namenode becomes ready so that they are slowed down. In this sense, we are better to perform the failover operation when the cluster is idea or under a small load.
Hope it helps.
Created 03-16-2017 09:16 PM
Before performing failover, it is a good idea to also check following: