- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ FOR ROCKETMQ SERVICE LEVEL AGREEMENT
- Contact Us
When a RocketMQ Cluster is no longer needed, it can be terminated and released.
Directions
You can delete a created virtual cluster by following the steps below:
1. On the Cluster Management list page, click Delete in the operations column.
2. In the deletion confirmation pop-up, click Delete to remove the cluster. After it is deleted, all configurations under the cluster will be cleared and cannot be recovered. Proceed with caution.
Note:
To prevent accidental deletion of internal data within the cluster (such as topics and groups), the console will perform a verification of resources within your cluster when attempting to delete it. If resources such as namespace, topic, or group have not been removed, the cluster cannot be deleted.
When deleting a namespace, first remove all topics and groups within the namespace, as batch deletion is now supported through the console. Before deleting the namespace, you also need to remove the namespace's affinity role. On the Namespace list page, click Configure Permissions.
After the permission configuration page is entered, click Delete to remove the affinity relationship between them. Afterward, you can return to the namespace page to delete the namespace.
To delete a created exclusive/generic cluster, follow the steps below:
1. On the Cluster list page, click the Terminate/Return button in the operation column.
2. On the Return Cluster page, confirm the cluster information. If there is a message backlog in the current cluster, a warning is displayed on this page.
3. After it is confirmed, proceed to Next, and the refund details and amount are displayed.
4. Once it is confirmed, the cluster enters an isolation state. Clusters in isolation cannot produce or consume messages. If clusters remain In Isolation for more than 7 days, it is automatically terminated.
5. For clusters in an isolation state, if you want to permanently delete the cluster, you can proceed to click the Terminate button in the operations column.
6. If you want to resume using the cluster during its isolation period, you can click the Recover button in the operations column during the isolation period to restore the metadata and configuration used during the period.
Yes
No
Was this page helpful?