Cluster cloning and high availability with multiple master nodes

You have learned about different cluster configurations, such as cluster scaling, debugging, and monitoring. Next, we will look at how to configure your EMR cluster to be highly available with multiple master nodes and how to clone an existing cluster that might be active or terminated.

High availability with multiple master nodes

Starting from EMR 5.23.0, you can launch an EMR cluster with multiple master nodes, which provides high availability for cluster applications such as YARN, HDFS NameNode, Spark, Hive, and Ganglia. You can use the EMR console or the AWS CLI to launch a cluster that has either one or three master nodes. If your cluster's primary master node fails or your NameNode or ResourceManager crashes, then EMR will automatically failover to stand by the master node, which makes the cluster fault-tolerant.

EMR automatically replaces the failed node with a new master node that has the same...