Delete a node from a primary ApsaraDB RDS for MySQL instance running RDS Cluster Edition to reduce compute capacity and associated costs when your cluster has spare capacity.
Deleting a node temporarily interrupts connections to that node. Other nodes continue to operate normally. To minimize impact on your workload, set the node's read weight to 0 before deleting it.
Prerequisites
Before you begin, ensure that:
-
The primary instance series is Cluster Edition
-
The instance status is Running
Billing
For billing changes after you delete a node, see Specification changes.
Procedure
A primary instance that runs RDS Cluster Edition must retain at least one primary node and one secondary node to ensure high availability.
-
Go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.
-
On the Basic Information page, go to the Instance Topology Management section and click Add Or Delete Node.
-
In the dialog box, select Delete Node and click Next.
-
Click the
icon to the left of the node you want to delete.NoteTo cancel the deletion, click Restore to the left of the node.
-
Read the terms of service and click Confirm Order.
What's next
After deleting the node, reconfigure the read/write attributes and read weights of the cluster read-only endpoint to redistribute traffic to the remaining nodes for load balancing.
To delete a node programmatically, use the DeleteDBNodes API operation.