Managing Nodes

Overview

On the Nodes tab page, you can view the node list of the current cluster, add new nodes to or remove nodes from it, and view the node usage, status, flavor, and AZ. In addition, you can click the icon next to the text in the Node Alias Name column of a specified node to modify the alias of the node. If the node does not have an alias, you can add an alias for the node.

Figure 1 Managing Nodes

• This feature is supported only in 8.1.1.200 or later cluster versions.
• The hybrid data warehouse (standalone) does not support node management.

Adding Nodes

This function is more suited for large-scale scale-out. Nodes can be added in batches in advance without interrupting services. For example, if 180 more BMS nodes are needed, add them in three batches (60 for each batch). If some nodes fail to be added, add them again. After all the 180 nodes are successfully added, use the nodes for cluster scale-out.

Precautions

• Nodes can be added only when no other task is running on the management side.
• The storage size of a new node must be the same as that of each of the existing nodes in the cluster.
• An added node, typically for scaling out, is referred to as an idle node. It starts incurring charges once added. You are advised to only add nodes when needed and promptly use them for scaling out.
• The anti-affinity rule dictates that the number of nodes to be added at a time must be an integer multiple of the cluster ring size. For example, if the cluster ring size is 3, the number of nodes to be added must be an integer multiple of 3.
• In the anti-affinity deployment mode, when a node is idle and fails due to power-off or other causes, it makes other nodes in its server group unavailable. In this case, you should remove and re-add the failed node.
• The anti-affinity rule dictates that, if a node fails to be added and is rolled back, other nodes that are being added in the same server group will also be rolled back.

Procedure

1. Log in to the GaussDB(DWS) console.
2. Choose Clusters > Dedicated Clusters. All clusters are displayed by default.
3. Click the name of the target cluster. On the Cluster Information page that is displayed, choose Nodes.
4. Click Add Node, enter the number of idle nodes to be added, and click Next: Confirm. If you create a BMS cluster, contact technical support to add the cluster to the whitelist for cross-flavor scale-out. After the cluster is whitelisted, Resource Flavor will be displayed on the Add Node page.If there are not enough IP addresses in the original subnet, you can add idle nodes from other subnets.
   Figure 2 Scaling out a BMS cluster across flavors
   
   

   In yearly/monthly mode, the time remaining and the expiration time are displayed.

5. After confirming that the information is correct, click Submit. The Nodes page is displayed. On this page, you can start adding nodes. Nodes that fail to be added are automatically rolled back and recorded in the failure list.

Removing Nodes

Precautions

• Nodes can be removed only when no other task is running on the management side.
• Only nodes whose resource status is Idle can be removed. Nodes that are in use cannot be removed.
• In anti-affinity deployment, nodes are removed by cluster ring. For example, when you remove a node, other nodes in the same ring will be automatically selected and displayed.
• In a yearly/monthly cluster during the grace period or retention period, nodes cannot be deleted. You can release nodes on the Renewals page of the Billing Center.

Procedure

1. Log in to the GaussDB(DWS) console.
2. Choose Clusters > Dedicated Clusters. All clusters are displayed by default.
3. Click the name of the target cluster. On the Cluster Information page that is displayed, choose Nodes.
4. On the Nodes page, select the node to be deleted and click Delete.
5. (Yearly/Monthly billing mode) The page for deletion confirmation is displayed.
6. Confirm the information and click OK. After the deletion is successful, the node is no longer displayed on the Nodes page.