Overview
You can delete a TDMQ for RabbitMQ cluster if you no longer need it.
The lifecycle of a TDMQ for RabbitMQ cluster is the process the cluster goes through from start to release. By properly managing the cluster lifecycle, you can ensure that the applications running in the cluster can provide services efficiently and economically. A cluster has the following status:
|
Creating | Intermediate status | The cluster is being created. |
Running | Stable status | The cluster is running normally, indicating that your node status, disk utilization, and other metrics are within the normal range. |
Deleting | Intermediate status | The cluster is being deleted in the console or via APIs. |
Isolated | Intermediate status | The cluster is in the 7-day isolation period after overdue payment. Production and consumption cannot be performed in a cluster in the isolated status, but the data and configurations saved in the cluster will not be deleted. |
Failed to create | Intermediate status | The cluster is purchased with fees successfully deducted in the console or via APIs but fails to be assigned. In this case, contact us for assistance. |
Deletion failed | Stable status | TDMQ for RabbitMQ fails to release resources after the cluster is manually deleted or isn't renewed within 7 days after expiration. |
Directions
Manual deletion
You can manually delete a monthly subscribed cluster before it expires by following the steps below:
2. On the left sidebar, select Cluster > Cluster. Then, click More > Terminate in the Operation column on the cluster list page.
3. In the Delete Confirmation pop-up window, delete the cluster after double confirmation. .
Note:
After a cluster is deleted, all its configurations will be cleared and cannot be recovered. Therefore, proceed with caution.
Automatic deletion upon expiration or overdue payment
Monthly subscribed instances can be retained in the TDMQ for RabbitMQ console for up to 7 calendar days after they expire or have overdue payments. You can continue to use them if you renew them within 7 days after expiration. For details, see Payment Overdue. If the TDMQ for RabbitMQ instance is not renewed within 7 days (inclusive) after expiration, its resources will be released at midnight on the 8th day, and data will be cleared and cannot be restored.
Note:
Production and consumption cannot be performed in a cluster in the isolated status, but the data and configurations saved in the cluster will not be deleted.
For clusters in the 7-day isolation status, you can go to the console to renew them by clicking Renew in the Operation column on the cluster list page. Successfully renewed clusters can go back to the running status and be normally used.
Was this page helpful?