Deleting Cluster
Last updated:2026-01-29 17:54:30
You can delete a TDSQL-C for MySQL cluster when it is no longer used. This document describes how to delete a cluster in the console.
Note:
After a cluster is deleted, all instances under it (including read-write instances and all read-only instances) are returned to the recycle bin. They will be permanently deleted after the retention period in the recycle bin expires.
After a cluster is deleted, all backup files associated with the cluster are deleted. Ensure to dump backup files in advance. If the read-write instances under the cluster are recovered within the recycle bin retention period, the corresponding backup files will also be recovered.
For pay-as-you-go clusters, after the deletion, a pay-as-you-go order is generated before billing completely stops due to the delayed billing mechanism.
If a monthly subscription cluster is deleted before it expires, the fees of all instances in it will be calculated again by the usage duration at the pay-as-you-go price, and your original payment will be refunded after fees incurred are deducted.
Use Cases
Delete the entire cluster.
Lifecycle
After a yearly/monthly subscription cluster is deleted, the instances under it are returned to the recycle bin and retained for 7 days, during which the instances are inaccessible. To recover such instances, renew the service in the recycle bin.
After a pay-as-you-go/Serverless cluster is deleted, the instances under it are returned to the recycle bin and retained for 3 days, during which the instances are inaccessible. To recover such instances, renew the service in the recycle bin.
Note：
For Serverless clusters, the scenario of renewal and recovery from the recycle bin is exclusively applicable to read-write instances. Read-only instances that have been reduced through the Read-Only Instance Management operation will not be isolated in the recycle bin but will be directly eliminated.
Directions
On the cluster list page, proceed based on the actually used view mode.
1. Log in to the TDSQL-C for MySQL console, and click the target cluster in the cluster list on the left to enter the cluster management page.
2. On the cluster management page, click Return/Refund on the right.
3. In the pop-up dialog box, view the instances to be terminated, confirm the information, and click Next.
4. Select one or more reasons for returning resources, select the option I have read and agree to Refund, and click Request a Return.
1. Log in to the TDSQL-C for MySQL console.
2. Find the target cluster in the cluster list and click More > Return/Refund in the Operation column.
3. In the pop-up dialog box, view the instances to be terminated, confirm the information, and click Next.
4. Select one or more reasons for returning resources, select the option I have read and agree to Refund, and click Request a Return.
Related APIs
API | Description |
This API (IsolateCluster) is used to isolate clusters. | |
This API (OfflineCluster) is used to destroy clusters. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback