Clone an existing E-MapReduce (EMR) cluster to create a new one with the same configurations. This saves time when you need to replicate a cluster setup without re-entering each setting manually.
Prerequisites
Before you begin, ensure that you have:
An existing DataLake, Dataflow, online analytical processing (OLAP), DataServing, or Custom cluster. For instructions, see Create a cluster
Limitations
Unsupported clusters: A cluster cannot be cloned if its product version, business scenario, or region is no longer supported.
Node groups: If an existing cluster has multiple node groups, only the Master, Core, and Task node groups can be cloned. If a node group uses multiple instance types, only the first instance type in the sort order is carried over.
Node count: If a node group has zero nodes, the minimum node count required for cluster creation is used. For example, a Task node group with 0 nodes is set to 1 node in the cloned cluster.
Billing method: If node groups in the source cluster use different billing methods, the cloned cluster defaults to pay-as-you-go. After the cluster is created, you can switch to subscription. For instructions, see Switch from pay-as-you-go to subscription.
Service configurations: Only custom service configurations at the cluster and node group levels are cloned, including changes made both during and after cluster creation.
vSwitch: If node groups use different vSwitches, the cloned cluster uses the most recently selected vSwitch.
Scaling rules: Only rules scheduled to trigger after the current time are cloned. For time-based periodic rules, the start time is adjusted as follows:
| Validity period | Behavior |
|---|---|
| Starts before the current time and ends before 00:00 the next day | Rule is not cloned |
| Starts before current time, ends after 00:00 the next day | Start time is reset to 00:00 the next day; end time is unchanged |
| Starts and ends after the current time | Start and end times are unchanged |
Not cloned: Files or content manually added to cluster nodes after cluster creation—such as JAR packages—are not carried over.
Known constraints
Clusters created before September 7, 2022 cannot be cloned if they are in the Create Failed, Release Failed, or Released state (incomplete cluster history).
For clusters created between September 7, 2022 and March 13, 2024, service configurations modified during cluster creation cannot be cloned (incomplete cluster history).
A released cluster can only be cloned if it was released within the last 60 days.
Clone a cluster from the cluster list
Log on to the EMR console. In the left-side navigation pane, click EMR on ECS.
In the top menu bar, select the target region and resource group.
On the EMR on ECS page, find the cluster you want to clone. In the Actions column, click
and select Clone.In the Warning dialog box, click Continue To Clone.
On the cluster creation page, confirm the cloned configurations, provide any required information, accept the terms of service, and confirm the order.
NoteFields that require your input are indicated on the page.