You can use the cluster cloning feature provided by E-MapReduce (EMR) to quickly create a cluster based on an existing cluster.
Prerequisites
A DataLake cluster, Dataflow cluster, online analytical processing (OLAP) cluster, DataServing cluster, or custom cluster is created. For more information, see Create a cluster.
Limits
If the product version, business scenario, or region of an existing cluster is no longer supported, the cluster cannot be cloned.
Node groups
If an existing cluster has multiple types of node groups, only the master, core, and task node groups can be cloned to the new cluster.
If a node group contains nodes of multiple instance types, only the first instance type is used for the node group in the new cluster.
Nodes: If a node group does not contain nodes, the minimum number of nodes that are required to create a cluster are cloned to the new cluster. For example, if the number of nodes in a task node group is 0, one node is cloned to the task node group in the new cluster.
Billing method: If a cluster has multiple types of node groups and the billing methods of the node groups are different, the pay-as-you-go billing method is used in the new cluster. After the new cluster is created, you can change the billing method from pay-as-you-go to subscription. For more information, see Switch from pay-as-you-go to subscription.
Service configurations: For modifications that are made to your cluster during cluster creation or cluster use, only the custom service modifications at the cluster or node group level can be cloned.
vSwitch: If the cluster has multiple types of node groups and the vSwitches of the node groups are different, the vSwitch that is selected most recently is used in the new cluster.
Auto scaling rules: If auto scaling rules are configured for a cluster, only auto scaling rules whose trigger time is later than the current time can be cloned to the new cluster. If the auto scaling rules are triggered periodically based on a specific point in time and the start time of the rule validity period is earlier than the current time, the start time changes to 00:00 on the next day for the new cluster. Take note of the following items:
Auto scaling rules whose start time of the rule validity period is earlier than the current time and end time is earlier than 00:00 on the next day cannot be cloned to the new cluster.
Auto scaling rules whose start time of the rule validity period is earlier than the current time and end time is later than 00:00 on the next day can be cloned to the new cluster. The start time changes to 00:00 on the next day for the new cluster, and the end time does not change.
Auto scaling rules whose start time and end time of the rule validity period are later than the current time can be cloned to the new cluster. The start time and end time remain unchanged for the new cluster.
Uncloned information: Modifications to files or content of nodes in a cluster, such as JAR packages, after the cluster is created cannot be cloned to the new cluster.
Precautions
If your cluster was created before September 7, 2022 and is in the Create Failed, Release Failed, or Released state, the cluster cannot be cloned because the historical records of the cluster are incomplete.
If your cluster was created between September 7, 2022 and March 13, 2024, the modifications made to the services of the cluster during cluster creation cannot be cloned to the new cluster because the historical records of the cluster are incomplete.
You can clone a cluster in the Released state only if the cluster is released within the previous 60 days.
Procedure
Log on to the EMR console. In the left-side navigation pane, click EMR on ECS.
In the top navigation bar, select the region in which your cluster resides and select a resource group based on your business requirements.
On the EMR on ECS page, find the cluster that you want to clone, move the pointer over the icon in the Actions column, and then select Clone.
In the Cluster Cloning Reminder message, read the information and click Continue to Clone.
In the cluster creation wizard, specify values for parameters that need to be manually configured. In the Confirm step, confirm all the configurations, read the terms of service, select the check box, and then click Confirm.
NoteThe parameters that need to be manually configured vary based on the specific cluster information.