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.
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. |
Nodes cannot be added to a storage-compute coupled data warehouse (standalone). |
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. |
A storage-compute coupled data warehouse (cluster mode) cannot be scaled in to a standalone cluster. |
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:
|
Currently, only storage-compute coupled clusters are supported. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.