E-MapReduce:Clone a cluster

Prerequisites

A DataLake, Dataflow, online analytical processing (OLAP), DataServing, or Custom cluster has been created. For more information, see Create a cluster.

Limitations

• A cluster cannot be cloned if its product version, business scenario, or region is no longer supported.

• Node group specifications:

  • 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 cloned.

• Number of nodes: If a node group has zero nodes, the minimum number of nodes required for cluster creation is used. For example, if a Task node group has 0 nodes, the number of nodes for that node group is set to 1 when the cluster is cloned.

• Billing method: If the node groups in an existing cluster have different billing methods, the pay-as-you-go billing method is used for the new cluster. After the cluster is created, you can change the billing method from pay-as-you-go to subscription as needed. For more information, see Switch from pay-as-you-go to subscription.

• Service configurations: If a cluster has modified service configurations, including modifications made during and after cluster creation, only custom service configurations at the cluster and node group levels are cloned.

• vSwitch: If the node groups in a cluster use different vSwitches, the most recently selected vSwitch for the cluster is used by default.

• Scaling rules: If a cluster has configured scaling rules, only rules that are scheduled to trigger after the current time are cloned. For time-based periodic rules, if the start time is earlier than the current time, the start time is changed to 00:00 on the next day. The specific rules are as follows:

  • The rule is not cloned if its validity period starts before the current time and ends before 00:00 on the next day.

  • If the validity period starts before the current time and ends after 00:00 on the next day, the start time is changed to 00:00 on the next day. The end time remains the same as that of the original rule.

  • If the validity period starts and ends after the current time, the start and end times remain the same as those of the original rule.

• Information that is not cloned: Files or content that you manually modify on cluster nodes after cluster creation, such as JAR packages, are not cloned to the new cluster.

Precautions

• Clusters created before September 7, 2022 cannot be cloned if they are in the Create Failed, Release Failed, or Released state. This is because their cluster history is incomplete.

• For clusters created between September 7, 2022 and March 13, 2024, service configurations modified during cluster creation cannot be cloned because the cluster history is incomplete.

• You can clone a released cluster only if it was released within the last 60 days.

Procedure

1. Log on to the EMR console. In the left-side navigation pane, click EMR on ECS.

2. In the top menu bar, select the desired region and resource group.

3. On the EMR on ECS page, find the target cluster and choose > Clone from the Actions column.

4. Read the message in the Warning dialog box, and then click Continue To Clone.

5. You are redirected to the cluster creation page. Confirm the cloned configurations, provide the required information, accept the terms of service, and then confirm the order.

   Note

   The specific information that you must provide is indicated on the page.