Help Center/ GaussDB(DWS)/ FAQs/ Cluster Management/ How Do I Determine When to Perform Node Flavor Change, All Specification Change, Scale-Out, or Scale-In for GaussDB(DWS)?
Updated on 2025-07-22 GMT+08:00
View PDF
Share

How Do I Determine When to Perform Node Flavor Change, All Specification Change, Scale-Out, or Scale-In for GaussDB(DWS)?

Resizing a cluster has a great impact on your workloads. It is similar to migrating an old cluster to a new one, with changes on nodes and specifications. You are advised to perform lightweight operations, such as scale-out, scale-in, and flavor change. The following table lists the application scenarios of the cluster modification options.

Table 1 Cluster modification options

Option

Scenario

Remarks

Scale-out

If your business grows and you have higher requirements on storage capacity and performance, or the CPU of your cluster is insufficient, you are advised to scale out your cluster.

-

Scale-in

During off-peak hours when a large amount of cluster capacity is idle, you can reduce the number of nodes to reduce costs.

-

Changing the Node Flavor

This option changes cluster flavors (including CPU, memory, and others) to meet service requirements. It does not change the number of nodes.

Elastic specification change is supported only for storage-compute coupled clusters that use ECSs and EVS disks. You can choose Change node flavor to enable elastic specification change.

Changing all specifications

You can resize your cluster when:

  • Your clusters are BMS clusters or they do not support flavor change.
  • You want to change the cluster topology instead of scale-out or scale-in which simply adds nodes or delete nodes ring by ring.
  • Your cluster is aged and you want to change it to a new cluster without migrating data.

Currently, only storage-compute coupled clusters are supported.
Parent topic: Cluster Management