Deleting Instance
Download
포커스 모드
폰트 크기
When an instance is no longer in use, you can delete it. This document describes how to delete an instance under a cluster.
Note:
Once a read-write instance is deleted, its data cannot be retrieved. The backup files are also deleted, and data recovery is not possible in the cloud. Please back up your files in advance.
During the isolation period after instance deletion, IP address resources remain occupied. IP address resources are released when the instance is deleted and taken offline. Before deletion, ensure that no services need to access the instance.
When you directly delete a cluster, all instances under the cluster are deleted.
Data is deleted only after the read-write instance is deleted. Deleting a read-only instance only removes its compute resources.
Scenarios
When a cluster's instance mode is provisioned resources, you can delete read-only instances under the cluster. After all read-only instances under the cluster are deleted, you can delete the read-write instance under that cluster. Deleting the read-write instance also deletes the cluster.
When a cluster's instance mode is Serverless and its architecture is the cluster edition, you cannot delete a read-write instance or a read-only instance individually. To reduce the number of read-only instances, refer to Read-Only Instance Management. When the architecture is the single-node edition, deleting the read-write instance deletes the entire cluster.
Lifecycle
After a yearly/monthly subscription instance is deleted, it is moved to the recycle bin and retained for 7 days. During this period, the instance is inaccessible. If you want to restore the instance, you can renew it in the recycle bin.
After a pay-as-you-go/Serverless instance is deleted, it is moved to the recycle bin and retained for 3 days. During this period, the instance is inaccessible. If you want to restore the instance, you can renew it in the recycle bin.
Note:
For Serverless clusters, restoring from the recycle bin applies only to read-write instances. Read-only instances reduced via Read-Only Instance Management are not isolated in the recycle bin but are taken offline directly.
Operation Steps
On the cluster list page, perform operations based on the actual view mode used:
1. Log in to the TDSQL-C for MySQL console and click the target cluster in the cluster list on the left to go to the Cluster Management page.
2. On the cluster details page, locate the target instance and click Return/Refund.
3. In the pop-up dialog box, after reading or selecting Confirm selected items > Check return details > Select the return reason, click Request a Return.
1. Log in to the TDSQL-C for MySQL console. In the cluster list, locate the cluster for which you need to delete instances. Click the cluster ID or Manage in the Operation column to go to the cluster management page.
2. On the cluster management page, select the Instance List tab, locate the read-write instance or read-only instance you want to delete, and then choose More > Return/Refund.
3. In the pop-up dialog box, after reading or selecting Confirm selected item > Check return details > Select the return reason, click Request a Return.
Related APIs
API | Description |
This API (OfflineInstance) is used to terminate an instance. |
피드백