Resizing a Cluster

Scenario

A cluster size specifies the maximum number of nodes a cluster can manage. If the current cluster size cannot meet your requirements, you can resize it.

Constraints

• The number of master nodes cannot be changed during cluster resizing.
• During cluster resizing, master nodes update in rolling fashion. Cluster management functions are temporarily restricted during this process. To minimize the impact on services, resize a cluster during off-peak hours. Do not perform other operations (such as creating workloads) during this period.
• When the master node flavor of an HA cluster is changed, a rolling update is used. Master nodes are preferentially distributed in the original AZ. If resources in the original AZ are insufficient, the nodes are scheduled to other AZs while ensuring that the DR specifications of the AZs are not degraded. If neither condition can be met, the flavor change may fail.
• If a cluster size is changed to 1,000 nodes or more, some parameters will be adjusted accordingly to ensure cluster performance. For details, see Modifying Cluster Configurations.
• After a cluster is resized, verify that installed add-ons have adequate resource quotas to meet workload requirements. For details, see How Do I Configure the Add-on Resource Quotas Based on Cluster Scale?

Billing

Cluster management fees are adjusted according to the new flavor. For details, see CCE Price Calculator.

Manually Upgrading the Master Node Flavor

1. Log in to the CCE console. In the navigation pane, choose Clusters.
2. In the cluster list on the right, locate the target cluster. Click and choose Modify Specifications from the drop-down list.
3. On the displayed page, select a larger cluster size.
   

   For service availability, single-master clusters are limited to fewer than 1,000 worker nodes.

4. Click Next to confirm the specifications and click OK. Resizing a cluster takes under 30 minutes, though the exact duration depends on cluster size.

   You can click Operation Records in the upper right corner to view the cluster change history. The status changes from Executing to Successful once the cluster size has been updated.

Helpful Links

When a cluster scales to 1,000 or more worker nodes, certain parameters are automatically tuned for optimal performance. For details, see Modifying Cluster Configurations.