E-MapReduce:Clone a cluster

Prerequisites

You have an existing DataLake, Dataflow, online analytical processing (OLAP), DataServing, or Custom cluster. For more information, see Create a cluster.

Limitations

• You cannot clone a cluster if the product version, business scenario, or region of the source cluster is no longer supported.

• Node group specifications:

  • If the source cluster has multiple node groups, only the Master, Core, and Task node groups can be restored.

  • If a node group includes multiple instance types, only the first instance type in the sort order can be restored.

• Node count: If the node count of a node group is 0, it is restored to the minimum node count required for cluster creation. For example, if a Task node group has 0 nodes, its node count is restored to 1 during cloning.

• Billing method: If node groups in the source cluster use different billing methods, the cloned cluster defaults to the pay-as-you-go method. After the cluster is created, you can switch from pay-as-you-go to subscription based on your needs. For more information, see Switch from pay-as-you-go to subscription.

• Service configuration: If the source cluster's service configuration was modified, only custom configuration at the cluster and node group levels is restored, regardless of whether the modifications were made during or after cluster creation.

• vSwitch: If node groups in the source cluster use different VSwitches, the cloned cluster defaults to the vSwitch most recently selected for the source cluster.

• Scaling rules: If scaling rules are configured for the source cluster, the cloning process restores only rules that are scheduled to trigger after the current time. For time-based periodic rules, if the start time is earlier than the current time, the start time is adjusted to 00:00 on the next day. The rules are adjusted as follows:

  • If the rule's validity period starts before the current time and ends before 00:00 on the next day, the rule is not restored.

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

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

• Information that is not cloned: The cloning process does not copy files or content manually added to the source cluster's nodes, such as a JAR package.

Notes

• Clusters created before September 7, 2022 cannot be cloned if they are in the Create Failed, Release Failed, or Released state, due to incomplete cluster history data.

• For clusters created between September 7, 2022, and March 13, 2024, service configuration modified during cluster creation cannot be restored during cloning due to incomplete history data.

• You can clone a Released cluster only within 60 days of its release.

Procedure

1. Log on to the E-MapReduce console.

2. In the top navigation bar, select a region and a resource group based on your needs.

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

4. In the Warning dialog box, read the message carefully and click Continue to Clone.

5. This action opens the cluster creation page. On this page, confirm the cloned information, enter the required information, accept the terms of service, and confirm the order.

   Note

   The console highlights the required information.