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-03-2016 01:55 AM
Ambari has a handy wizard for helping move a NameNode from one machine to another. In the event something were to go wrong with the move in, say, a NameNode HA enviornment are there any recommendations on how to recover and restore the NameNode setup back to its original server? Would the move NameNode wizard be the best approach to putting the server back or would the Ambari API be a better approach?
Created 02-05-2016 10:36 PM
As per a Support note:
"You can use the Move NameNode wizard in Ambari. This will move the NameNode but only according to Ambari.
After this has been successfully completed (with the NameNode down) then you should move all the files in the old namenode edits directory (dfs.namenode.name.dir) to the new NameNode in the directory configured. The permissions of these files will be hdfs:hadoop (by default) but the owner should be the user who runs your NameNode & the group will be the hadoop primary group.
After this is done, then the NameNode is ready to start."
The most important thing is to ensure that you have a backup of all the images and edits in dfs.namenode.name.dir. Then if anything happens you can you can revert back to that.
Created 02-03-2016 05:41 AM
@Kent Baxley I think little bit more information will help. Is NN HA part of the picture?
Created 02-05-2016 10:36 PM
As per a Support note:
"You can use the Move NameNode wizard in Ambari. This will move the NameNode but only according to Ambari.
After this has been successfully completed (with the NameNode down) then you should move all the files in the old namenode edits directory (dfs.namenode.name.dir) to the new NameNode in the directory configured. The permissions of these files will be hdfs:hadoop (by default) but the owner should be the user who runs your NameNode & the group will be the hadoop primary group.
After this is done, then the NameNode is ready to start."
The most important thing is to ensure that you have a backup of all the images and edits in dfs.namenode.name.dir. Then if anything happens you can you can revert back to that.