09-04-2017 12:17 AM
Did you tried the ec2 instance replacement of the nodes with other master services such as hive,hue spark etc ?
I am thinking of the below strategy,let me know your views on it.
09-07-2017 02:36 PM - edited 09-07-2017 02:39 PM
There is stateless and stateful master.
For stateless master, you should be able to switch instances. For stateful master, it is a little bit complicated, it might be good to keep EBS snapshot, but the snapshot is not online replica, that you might need to do some manual work to recover from failure.
But those are only from the point of the view of individual instance, the configuration of master(s) might be recorded somewhere else, eg zookeeper, that you also need to refresh configuration afterwards if needed.
10-04-2017 03:43 AM
10-09-2017 07:06 AM
As I stated in a previous reply, replacing a Cloudera Manager instance is possible but complex, and isn't a first-class feature of Director.
If you find yourself in a situation where you regularly need to destroy and recreate instances, whether for Cloudera Manager or cluster services, then you should consider using transient clusters and storing your data on persistent storage services like S3 or ADLS. Then you can tear down clusters and create new ones without the complexities of in-place instance replacement.
10-17-2017 06:38 AM
Hello Bill ,
We have migrated the CM to a new instance.Using few tricks and director crash shell we were able to migrate the CM to a new instance.
Have anyone tried to migrate KTS instances on AWS .We cannot keep the same ip of the instances as recommended by cloudera .So can anyone share the steps where we migrate the KTS instance to a new instance with different ip as compared to previous instance ip.