Guidelines on Replacing Nodes in Hadoop cluster running on Azure VM's

[#1]

We are having a 6 node cluster ( 2 master and 3 slave nodes and 1 Edge Node) on AWS VM's deployed using Ambari. I need to replace the old VM's with VM's of increased size and memory.. What would be the best startegy t o replace the existing 3 slave nodes with a new set of slave nodes with a different instance type. Since we have some data in HDFS. what would be the best strategy to retain the data and bring up the cluster with new nodes.

Will it be advisable to replace Namenode or just Slave Nodes and Edge Node?

[#2]

@Artem Ervits

Yes thats what my understanding is. Thanks for confirming.

By any chance is there a plan in future for cloudbreak to deploy cluster on already running VM's in cloud?

[#3]

@rahul gulati

not sure, I'm not privy to the Cloudbreak roadmap. Perhaps you'd want to open this as a new HCC question and someone from the Cloudbreak team can respond?

[#4]

@Artem Ervits

Ok sure. Just wanted to know about Namenode as well in case that also needs an upgrade to VM of higher memory and CPU. What should be the ideal scenario in that case?

Thanks

[#5]

Add two new nodes, then in Ambari there's an option to move namenode in the HDFS section.

[#6]

@Artem Ervits

> Both can add and remove instances as well as provision new instances with new machine type easily.

Could you please point where that option could be located in the UI or CLI of Cloudbreak? Thank you!