Tencent Cloud

Recent Pages

Deleting Instance

Last updated: 2024-09-10 09:37:29

This document describes how to delete an instance from a cluster when it is  no longer used.
Note: 
After a read-write instance is deleted, its data and backup files will also be deleted and cannot be recovered in the cloud. Store your backup files safely elsewhere in advance.
After an instance is deleted, its IP resources will also be released. Therefore, confirm that your business no longer needs to access the instance before deleting it.
If you delete a cluster, all instances in the cluster will be deleted.
Data is deleted only when the read-write instance is deleted. Deleting read-only instances only deletes computing resources.
Use Cases
When the cluster has pre-configured resources as its instance type, deleting read-only instances under the cluster is supported. The read-write instance can only be deleted after all read-only instances under the cluster have been removed. After the read-write instance is deleted, the cluster is also deleted.
When the cluster has Serverless as its instance type, and the architecture is set to cluster mode, it is not possible to delete read-write instances or read-only instances individually. To reduce the number of read-only instances, one must refer to the Read-Only Instance Management guidelines. Conversely, when the architecture is set to a single-node mode, deleting the read-write instance equates to the deletion of the entire cluster.
Lifecycle
After a monthly-subscribed instance is deleted, it will be moved to the recycle bin and retained there for seven days. During the retention period, the instance cannot be accessed, but it can be restored after renewal.
After a pay-as-you-go/serverless instance is deleted, it is moved to the recycle bin and retained there for three days. During the retention period, the instance cannot be accessed. If you want to restore the instance, you can renew the instance in the recycle bin.
Note：
For Serverless clusters, the scenario of restoration 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:
Tab View
List View
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. Under Cluster Details, find the target instance and Click on Return/Refund.
﻿
3. In the pop-up dialog box, after reading or checking the  Confirm selected items  >  Check return details  >  Select the return reason , click  Request a Return .
﻿
1. Log in to the TDSQL-C for MySQL console and click the ID of the target cluster in the cluster list or Manage in the Operation column to enter the cluster management page.
2. On the cluster management page, select the Instance List tab, find the target read-write or read-only instance, and select More > Return/Refund in the Operation column.
﻿
3. In the pop-up dialog box, after reading or checking the  Confirm selected item  >  Check return details  >  Select the return reason , click  Request a Return .
﻿