Changing the Node Flavor
Function
If your cluster does not have sufficient compute resources, such as CPUs and memory, to meet growing service requirements, you may need to upgrade the cluster configuration. When service requirements decline, your cluster may have more resources than needed, and you need to downgrade the cluster configuration to avoid waste and reduce costs. Traditionally, you would need to create another cluster or delete the existing cluster and create another one to meet requirements, which is both costly and time-consuming. By changing the node flavor, you can dynamically adjust the CPUs and memory of each node in a cluster to respond to requirement changes, without changing the number of nodes or the amount of stored data. For more information, see Supported node flavors.
You can modify the CPU and memory configurations of the VM nodes in the target cluster by utilizing the underlying ECS capabilities. The following figure illustrates this process.
- To prevent service disruptions, it is crucial to schedule the elastic flavor change time window properly since the cluster must be restarted during the entire process.
- Changing all nodes in rolling mode or concurrently ensures that the process will not take longer due to the number of nodes. Typically, the entire process takes around 20 minutes.
Application Scenarios
- Periodic peaks: Workloads have obvious periodic peaks and troughs. Compute needs to be quickly enhanced before a peak to meet requirements and reduced after it to save costs.
- Only compute changes: Workloads require CPU and memory adjustment, but do not require changes in storage capacity and node quantity.
Example: An e-commerce website needs enhanced compute to handle the surge in query requests during a promotion. Before the promotion, they can change the cluster flavor from dwsx2.4xlarge.m7 to dwsx2.8xlarge.m7. After the promotion, they can change the flavor back to the original one to minimize costs.
Node Flavor Change Modes
DWS supports online and offline node flavor changes. For details, see Table 1.
| Node Flavor Change Mode | Description |
|---|---|
| Offline | During the change, the cluster will be stopped. Services will be unavailable for about 10 minutes. The offline mode is used by default. |
| Online | Changes are applied to nodes one at a time. Services may be interrupted briefly (3 to 5 times) during the change. In addition, the performance of decoupled storage and compute will deteriorate briefly. DDL services are unavailable during flavor changes of CNs. An online flavor change takes a longer time than an offline flavor change. Plan your time window carefully. If the online mode is not supported on the console, contact technical support. |
Precautions
- Choosing a lower target flavor can impact cluster performance. Evaluate the potential impact on services before proceeding with the operation.
- Check if there are sufficient ECS resources and tenant CPU quotas in the current region before changing the flavor.
- You can retry a flavor change. If the flavor of some nodes fails to change, you can submit the change task again. The system will continue the unfinished change process instead of starting from the beginning.
Constraints and Limitations
- Only cluster versions 8.1.1.300 and later support elastic flavor change. For an earlier version, contact technical support to upgrade it first.
- Only management plane of version 8.6.1 or later supports online node flavor changes. If the online mode is not supported on the console, contact technical support.
- This function is only supported by storage-compute coupled and decoupled clusters that use ECSs and EVS disks. It is unavailable for clusters using ECSs with local disks.
ECSs with EVS disks and ECSs with local disks differ in the storage mount mode. EVS disks are network block storage and support flavor changes. ECSs with local disks use local storage of physical machines and do not support online flavor changes.
Procedure
- Log in to the DWS console.
- Choose Cluster > Cluster List. All clusters are displayed by default.
- In the row of a cluster, choose More > Change Specifications > Change node flavor in the Operation column. Click OK.
- On the Change node flavor page, select the target flavor and change mode.
Table 2 Flavor change parameters Parameter
Description
Change Specifications
Select the target flavor.
- (Default) You can select a flavor of the same type as the current flavor. For details about the supported flavors, see Table 3.
- You can also select a flavor of a type different from the current flavor. If it is not supported, contact technical support.
Change Mode
You can select Online or Offline. For details, see Table 1.
Figure 2 Changing the flavor
- Confirm the settings, select the confirmation check box, and click Next: Confirm.
- Click Submit. In the displayed dialog box, click OK to submit the cluster flavor change task.
- Confirm the information and click Submit. If the billing mode is yearly/monthly, you will be redirected to the payment page.
- Return to the cluster list. The cluster status will change to Changing node flavor. Wait for about 20 minutes.
Hybrid Billing for Flavor Changes in a Yearly/Monthly Billed Cluster
Only storage-compute decoupled clusters support hybrid billing.
Precautions
During peak hours, nodes can be automatically added to a yearly/monthly cluster through scheduled addition of virtual warehouses. The added nodes are billed on a pay-per-use basis. For details, see Elastically Adding or Deleting DWS Virtual Warehouses (Storage-Compute Decoupled Cluster). After the scale-out, the cluster uses hybrid billing, that is, some nodes are billed on a pay-per-use basis, while the others are billed on a yearly/monthly basis.
- Yearly/Monthly nodes: nodes purchased during cluster creation
- Pay-per-use nodes: nodes automatically added through a scaling plan
Procedure
- Log in to the DWS console.
- In the navigation pane on the left, choose Cluster > Cluster List.
- Click Create DWS Cluster to create a storage-compute decoupled cluster if needed. For details, see Creating a DWS Storage-Compute Decoupled Cluster.
- After the cluster is created, add a node addition or deletion plan. After nodes are automatically added, if you want to upgrade specifications, locate the row that contains the cluster, click More in the Operation column and select Change Specifications and then Change disk capacity. The hybrid billing page is displayed, showing the following information:
- Additional fee: the fee that needs to be paid for this flavor upgrade
- Configuration fee: the hourly price of pay-per-use nodes after the flavor upgrade
Supported Flavors
| Current Flavor Name | Target Flavor Name |
|---|---|
| dwsk2.xlarge | dwsk2.2xlarge, dwsk2.4xlarge, dwsk2.12xlarge, dwsk2.8xlarge |
| dwsk2.2xlarge | dwsk2.12xlarge, dwsk2.8xlarge, dwsk2.4xlarge |
| dwsk2.4xlarge | dwsk2.2xlarge, dwsk2.8xlarge, dwsk2.12xlarge |
| dwsk2.8xlarge | dwsk2.2xlarge, dwsk2.4xlarge, dwsk2.12xlarge |
| dwsk2.12xlarge | dwsk2.2xlarge, dwsk2.4xlarge, dwsk2.8xlarge |
| dwsk2.h.12xlarge.4.kc1 | dwsk2.h.xlarge.4.kc1, dwsk2.h.2xlarge.4.kc1, dwsk2.h.4xlarge.4.kc1, dwsk2.h.8xlarge.4.kc1 |
| dwsk2.h.2xlarge.4.kc1 | dwsk2.h.8xlarge.4.kc1, dwsk2.h.12xlarge.4.kc1, dwsk2.h.xlarge.4.kc1, dwsk2.h.4xlarge.4.kc1 |
| dwsk2.h.4xlarge.4.kc1 | dwsk2.h.8xlarge.4.kc1, dwsk2.h.12xlarge.4.kc1, dwsk2.h.xlarge.4.kc1, dwsk2.h.2xlarge.4.kc1 |
| dwsk2.h.8xlarge.4.kc1 | dwsk2.h.xlarge.4.kc1, dwsk2.h.2xlarge.4.kc1, dwsk2.h.4xlarge.4.kc1, dwsk2.h.12xlarge.4.kc1 |
| dwsk2.h.xlarge.4.kc1 | dwsk2.h.2xlarge.4.kc1, dwsk2.h.4xlarge.4.kc1, dwsk2.h.8xlarge.4.kc1, dwsk2.h.12xlarge.4.kc1 |
| dwsk2.h1.12xlarge.4.kc1 | dwsk2.h1.4xlarge.4.kc1, dwsk2.h1.8xlarge.4.kc1, dwsk2.h1.2xlarge.4.kc1 |
| dwsk2.h1.2xlarge.4.kc1 | dwsk2.h1.4xlarge.4.kc1, dwsk2.h1.8xlarge.4.kc1, dwsk2.h1.12xlarge.4.kc1 |
| dwsk2.h1.4xlarge.4.kc1 | dwsk2.h1.8xlarge.4.kc1, dwsk2.h1.12xlarge.4.kc1, dwsk2.h1.2xlarge.4.kc1 |
| dwsk2.h1.8xlarge.4.kc1 | dwsk2.h1.4xlarge.4.kc1, dwsk2.h1.12xlarge.4.kc1, dwsk2.h1.2xlarge.4.kc1 |
| dwsk2.h1.xlarge.2.kc1 | dwsk2.h1.2xlarge.4.kc1, dwsk2.h1.4xlarge.4.kc1, dwsk2.h1.8xlarge.4.kc1, dwsk2.h1.12xlarge.4.kc1 |
| dwsx2.xlarge | dwsx2.2xlarge, dwsx2.4xlarge, dwsx2.8xlarge, dwsx2.16xlarge |
| dwsx2.2xlarge | dwsx2.4xlarge, dwsx2.8xlarge, dwsx2.16xlarge |
| dwsx2.4xlarge | dwsx2.2xlarge, dwsx2.8xlarge, dwsx2.16xlarge |
| dwsx2.8xlarge | dwsx2.2xlarge, dwsx2.4xlarge, dwsx2.16xlarge |
| dwsx2.16xlarge | dwsx2.2xlarge, dwsx2.4xlarge, dwsx2.8xlarge |
| dwsx2.xlarge.m7 | dwsx2.2xlarge.m7, dwsx2.4xlarge.m7, dwsx2.8xlarge.m7, dwsx2.16xlarge.m7 |
| dwsx2.2xlarge.m7 | dwsx2.4xlarge.m7, dwsx2.8xlarge.m7, dwsx2.16xlarge.m7 |
| dwsx2.4xlarge.m7 | dwsx2.2xlarge.m7, dwsx2.8xlarge.m7, dwsx2.16xlarge.m7 |
| dwsx2.8xlarge.m7 | dwsx2.2xlarge.m7, dwsx2.4xlarge.m7, dwsx2.16xlarge.m7 |
| dwsx2.16xlarge.m7 | dwsx2.2xlarge.m7, dwsx2.4xlarge.m7, dwsx2.8xlarge.m7 |
| dwsx2.xlarge.m7n | dwsx2.2xlarge.m7n, dwsx2.8xlarge.m7n, dwsx2.16xlarge.m7n |
| dwsx2.2xlarge.m7n | dwsx2.8xlarge.m7n, dwsx2.16xlarge.m7n |
| dwsx2.8xlarge.m7n | dwsx2.2xlarge.m7n, dwsx2.16xlarge.m7n |
| dwsx2.16xlarge.m7n | dwsx2.2xlarge.m7n, dwsx2.8xlarge.m7n |
| dwsx2.h.xlarge.4.c6 | dwsx2.h.2xlarge.4.c6, dwsx2.h.4xlarge.4.c6, dwsx2.h.8xlarge.4.c6, dwsx2.h.16xlarge.4.c6 |
| dwsx2.h.2xlarge.4.c6 | dwsx2.h.4xlarge.4.c6, dwsx2.h.8xlarge.4.c6, dwsx2.h.16xlarge.4.c6 |
| dwsx2.h.4xlarge.4.c6 | dwsx2.h.8xlarge.4.c6, dwsx2.h.16xlarge.4.c6, dwsx2.h.2xlarge.4.c6 |
| dwsx2.h.8xlarge.4.c6 | dwsx2.h.4xlarge.4.c6, dwsx2.h.16xlarge.4.c6, dwsx2.h.2xlarge.4.c6 |
| dwsx2.h.16xlarge.4.c6 | dwsx2.h.2xlarge.4.c6, dwsx2.h.4xlarge.4.c6, dwsx2.h.8xlarge.4.c6 |
| dwsx2.h.xlarge.4.c7 | dwsx2.h.4xlarge.4.c7, dwsx2.h.8xlarge.4.c7, dwsx2.h.16xlarge.4.c7, dwsx2.h.2xlarge.4.c7 |
| dwsx2.h.2xlarge.4.c7 | dwsx2.h.4xlarge.4.c7, dwsx2.h.8xlarge.4.c7, dwsx2.h.16xlarge.4.c7 |
| dwsx2.h.4xlarge.4.c7 | dwsx2.h.2xlarge.4.c7, dwsx2.h.8xlarge.4.c7, dwsx2.h.16xlarge.4.c7 |
| dwsx2.h.8xlarge.4.c7 | dwsx2.h.16xlarge.4.c7, dwsx2.h.2xlarge.4.c7, dwsx2.h.4xlarge.4.c7 |
| dwsx2.h.16xlarge.4.c7 | dwsx2.h.8xlarge.4.c7, dwsx2.h.xlarge.4.c7, dwsx2.h.2xlarge.4.c7, dwsx2.h.4xlarge.4.c7 |
| dwsx2.h.xlarge.4.c7n | dwsx2.h.2xlarge.4.c7n, dwsx2.h.4xlarge.4.c7n, dwsx2.h.8xlarge.4.c7n, dwsx2.h.16xlarge.4.c7n |
| dwsx2.h.2xlarge.4.c7n | dwsx2.h.4xlarge.4.c7n, dwsx2.h.8xlarge.4.c7n, dwsx2.h.16xlarge.4.c7n |
| dwsx2.h.4xlarge.4.c7n | dwsx2.h.2xlarge.4.c7n, dwsx2.h.8xlarge.4.c7n, dwsx2.h.16xlarge.4.c7n |
| dwsx2.h.8xlarge.4.c7n | dwsx2.h.16xlarge.4.c7n, dwsx2.h.2xlarge.4.c7n, dwsx2.h.4xlarge.4.c7n |
| dwsx2.h.16xlarge.4.c7n | dwsx2.h.4xlarge.4.c7n, dwsx2.h.8xlarge.4.c7n, dwsx2.h.2xlarge.4.c7n |
| dwsx2.h1.xlarge.2.c6 | dwsx2.h1.8xlarge.4.c6, dwsx2.h1.16xlarge.4.c6, dwsx2.h1.2xlarge.4.c6, dwsx2.h1.4xlarge.4.c6 |
| dwsx2.h1.2xlarge.4.c6 | dwsx2.h1.4xlarge.4.c6, dwsx2.h1.8xlarge.4.c6, dwsx2.h1.16xlarge.4.c6 |
| dwsx2.h1.4xlarge.4.c6 | dwsx2.h1.2xlarge.4.c6, dwsx2.h1.8xlarge.4.c6, dwsx2.h1.16xlarge.4.c6 |
| dwsx2.h1.8xlarge.4.c6 | dwsx2.h1.16xlarge.4.c6, dwsx2.h1.4xlarge.4.c6, dwsx2.h1.2xlarge.4.c6 |
| dwsx2.h1.16xlarge.4.c6 | dwsx2.h1.4xlarge.4.c6, dwsx2.h1.2xlarge.4.c6, dwsx2.h1.8xlarge.4.c6 |
| dwsx2.h1.xlarge.2.c7 | dwsx2.h1.4xlarge.4.c7, dwsx2.h1.8xlarge.4.c7, dwsx2.h1.16xlarge.4.c7, dwsx2.h1.2xlarge.4.c7 |
| dwsx2.h1.16xlarge.4.c7 | dwsx2.h1.4xlarge.4.c7, dwsx2.h1.8xlarge.4.c7, dwsx2.h1.2xlarge.4.c7 |
| dwsx2.h1.2xlarge.4.c7 | dwsx2.h1.4xlarge.4.c7, dwsx2.h1.8xlarge.4.c7, dwsx2.h1.16xlarge.4.c7 |
| dwsx2.h1.4xlarge.4.c7 | dwsx2.h1.2xlarge.4.c7, dwsx2.h1.8xlarge.4.c7, dwsx2.h1.16xlarge.4.c7 |
| dwsx2.h1.8xlarge.4.c7 | dwsx2.h1.4xlarge.4.c7, dwsx2.h1.2xlarge.4.c7, dwsx2.h1.16xlarge.4.c7 |
| dwsx2.h1.xlarge.2.c7n | dwsx2.h1.2xlarge.4.c7n, dwsx2.h1.4xlarge.4.c7n, dwsx2.h1.8xlarge.4.c7n, dwsx2.h1.16xlarge.4.c7n |
| dwsx2.h1.2xlarge.4.c7n | dwsx2.h1.16xlarge.4.c7n, dwsx2.h1.4xlarge.4.c7n, dwsx2.h1.8xlarge.4.c7n |
| dwsx2.h1.4xlarge.4.c7n | dwsx2.h1.8xlarge.4.c7n, dwsx2.h1.16xlarge.4.c7n, dwsx2.h1.2xlarge.4.c7n |
| dwsx2.h1.8xlarge.4.c7n | dwsx2.h1.4xlarge.4.c7n, dwsx2.h1.16xlarge.4.c7n, dwsx2.h1.2xlarge.4.c7n |
| dwsx2.h1.16xlarge.4.c7n | dwsx2.h1.2xlarge.4.c7n, dwsx2.h1.4xlarge.4.c7n, dwsx2.h1.8xlarge.4.c7n |
| dwsx2.rt.xlarge.m7 | dwsx2.rt.2xlarge.m7, dwsx2.rt.4xlarge.m7, dwsx2.rt.8xlarge.m7, dwsx2.rt.16xlarge.m7 |
| dwsx2.rt.2xlarge.m7 | dwsx2.rt.4xlarge.m7, dwsx2.rt.8xlarge.m7, dwsx2.rt.16xlarge.m7 |
| dwsx2.rt.4xlarge.m7 | dwsx2.rt.2xlarge.m7, dwsx2.rt.8xlarge.m7, dwsx2.rt.16xlarge.m7 |
| dwsx2.rt.8xlarge.m7 | dwsx2.rt.2xlarge.m7, dwsx2.rt.4xlarge.m7, dwsx2.rt.16xlarge.m7 |
| dwsx2.rt.16xlarge.m7 | dwsx2.rt.2xlarge.m7, dwsx2.rt.4xlarge.m7, dwsx2.rt.8xlarge.m7 |
| dwsk2.rt.xlarge.km1 | dwsk2.rt.2xlarge.km1, dwsk2.rt.4xlarge.km1, dwsk2.rt.8xlarge.km1, dwsk2.rt.12xlarge.km1 |
| dwsk2.rt.2xlarge.km1 | dwsk2.rt.4xlarge.km1, dwsk2.rt.8xlarge.km1, dwsk2.rt.12xlarge.km1 |
| dwsk2.rt.4xlarge.km1 | dwsk2.rt.2xlarge.km1, dwsk2.rt.8xlarge.km1, dwsk2.rt.12xlarge.km1 |
| dwsk2.rt.8xlarge.km1 | dwsk2.rt.2xlarge.km1, dwsk2.rt.4xlarge.km1, dwsk2.rt.12xlarge.km1 |
| dwsk2.rt.12xlarge.km1 | dwsk2.rt.2xlarge.km1, dwsk2.rt.4xlarge.km1, dwsk2.rt.8xlarge.km1 |
| dwsx2.rt.xlarge.m7n | dwsx2.rt.2xlarge.m7n, dwsx2.rt.8xlarge.m7n, dwsx2.rt.16xlarge.m7n |
| dwsx2.rt.2xlarge.m7n | dwsx2.rt.8xlarge.m7n, dwsx2.rt.16xlarge.m7n |
| dwsx2.rt.8xlarge.m7n | dwsx2.rt.2xlarge.m7n, dwsx2.rt.16xlarge.m7n |
| dwsx2.rt.16xlarge.m7n | dwsx2.rt.2xlarge.m7n, dwsx2.rt.8xlarge.m7n |
| 4U16G.4DPU | 8U32G.8DPU, 16U64G.16DPU, 32U128G.32DPU, 64U256G.64DPU, 96U384G.96DPU, 128U512G.128DPU |
| 8U32G.8DPU | 16U64G.16DPU, 32U128G.32DPU, 64U256G.64DPU, 96U384G.96DPU, 128U512G.128DPU |
| 16U64G.16DPU | 8U32G.8DPU, 32U128G.32DPU, 64U256G.64DPU, 96U384G.96DPU, 128U512G.128DPU |
| 32U128G.32DPU | 8U32G.8DPU, 16U64G.16DPU, 64U256G.64DPU, 96U384G.96DPU, 128U512G.128DPU |
| 64U256G.64DPU | 8U32G.8DPU, 16U64G.16DPU, 32U128G.32DPU, 96U384G.96DPU, 128U512G.128DPU |
| 96U384G.96DPU | 8U32G.8DPU, 16U64G.16DPU, 32U128G.32DPU, 64U256G.64DPU, 128U512G.128DPU |
| 128U512G.128DPU | 8U32G.8DPU, 16U64G.16DPU, 32U128G.32DPU, 64U256G.64DPU, 96U384G.96DPU |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
