tencent cloud

TDMQ for RocketMQ

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for RocketMQ
Strengths
Scenarios
Product Series
Comparison with Open-Source RocketMQ
High Availability
Quotas and Limits
Supported Regions
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Pay-as-you-go Switch to Monthly Subscription (5.x)
Renewal
Viewing Consumption Details
Refund
Overdue Payments
Getting Started
Getting Started Guide
Preparations
Step 1: Creating TDMQ for RocketMQ Resources
Step 2: Using the SDK to Send and Receive Messages (Recommended)
Step 2: Running the TDMQ for RocketMQ Client (Optional)
Step 3: Querying Messages
Step 4: Deleting Resources
User Guide
Usage Process Guide
Configuring Account Permissions
Creating the Cluster
Configuring the Namespace
Configuring the Topic
Configuring the Group
Connecting to the Cluster
Managing Messages
Managing the Cluster
Viewing Monitoring Data and Configuring Alarms
Cross-Cluster Message Replication
Use Cases
Naming Conventions for Common Concepts of TDMQ for RocketMQ
RocketMQ Client Use Cases
RocketMQ Performance Load Testing and Capacity Assessment
Access over HTTP
Client Risk Descriptions and Update Guide
Migration Guide for TencentCloud API Operations Related to RocketMQ 4.x Cluster Roles
Migration Guide
Disruptive Migration
Seamless Migration
Developer Guide
Message Types
Message Filtering
Message Retries
POP Consumption Mode (5.x)
Clustering Consumption and Broadcasting Consumption
Subscription Relationship Consistency
Traffic Throttling
​​API Reference(5.x)
History
API Category
Making API Requests
Topic APIs
Consumer Group APIs
Message APIs
Role Authentication APIs
Hitless Migration APIs
Cloud Migration APIs
Cluster APIs
Data Types
Error Codes
​​API Reference(4.x)
SDK Reference
SDK Overview
5.x SDK
4.x SDK
Security and Compliance
Permission Management
CloudAudit
Deletion Protection
FAQs
4.x Instance FAQs
Agreements
TDMQ for RocketMQ Service Level Agreement
Contact Us

Returning/Deleting a Cluster

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-23 17:34:05

Scenarios

When you no longer need a TDMQ for RocketMQ cluster, you can delete it. To avoid accidental cluster deletion, a yearly/monthly subscription cluster will enter a 7-day isolation period after initial deletion. During the isolation period, you can manually recover or delete the cluster. After the isolation period ends, the cluster will be completely deleted, and all data will be irrecoverable.

Constraints and Limitations

To prevent accidental deletion of internal cluster data (such as topics, groups, and roles) caused by misoperations, the console performs a verification process on your cluster resources during deletion. If resources such as topics or groups still exist, you are unable to delete the cluster.
For 4.x exclusive clusters/virtual clusters, delete the topics and groups in a namespace before deleting the namespace. Namespaces can be deleted in batches in the console. Before deleting a namespace, you also need to delete the roles bound to the namespace.
1.1 On the Namespace page, click Configure Permission in the operation column of a namespace in the namespace list.



1.2 On the permission configuration page, click Delete to unbind the two. Then, you can go to the namespace page again to delete the namespace.

Prerequisites

Deletion protection is not enabled for the cluster. If it is enabled, disable it before the deletion operation. For specific steps, see Configuring Deletion Protection.
The cluster status is "running (healthy/alarm)".

Operation Steps

Deleting and Returning Monthly Subscription Clusters
Deleting and Returning Pay-as-You-Go Clusters

Manual Return

For yearly/monthly subscription clusters that have not expired, you can manually return them. The steps are as follows:
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, choose Resource > Cluster, locate the target cluster, click More in the operation column, and select Terminate/Return from the drop-down list.
3. In the pop-up window for returning the cluster, confirm the cluster information. If messages are backlogged in the cluster, a reminder is displayed on the page.
4. After confirmation, select I have read and agreed to the refund rules and click Next. The refund details and amount are displayed. After verifying that the information is correct, click Confirm to return the cluster.
Note:
After a cluster is returned, it will be retained for 7 days (during which you can manually delete the cluster), and its status is displayed as Isolated. The cluster will be automatically deleted after 7 days.
Cluster configurations and metadata are retained for 7 days. Saved and unconsumed messages within the cluster are not retained. Therefore, back up data in advance.
For a cluster in an isolated status within 7 days, you can go to the Cluster List page in the console, click More in the operation column, and select Restore from the drop-down list. After successful renewal, the cluster is restored to the running status and can be used normally.
Under a single account, five-day (including the fifth day) unconditional full refund is supported for a purchased cluster. In other cases, the refund amount is returned to your Tencent Cloud account based on the proportion of cash and free credit used in the purchase.
For details on refund, see Refund.

Automatic Return Upon Expiration/in Arrears

A yearly/monthly subscription cluster can be retained in the TDMQ for RocketMQ console for up to 7 calendar days after expiration/in arrears. If renewal is completed within 7 days, the cluster can continue to be used. For details, see Overdue Payments.
If your TDMQ for RocketMQ cluster is not renewed within 7 days (including the 7th day) after expiration, the system will release the resources within approximately 24 hours. Data in expired clusters will be cleared, which is irrecoverable.

Deleting a Cluster

A yearly/monthly subscription cluster will be retained in the TDMQ for RocketMQ console for 7 days after being manually returned or automatically returned upon expiration/in arrears, and its status is displayed as Isolated. After 7 days (including the 7th day), it is completely released. During this period, you can manually delete the cluster.
Note:
If you delete a cluster, the cluster is immediately removed from the cluster list of your account. The cluster can no longer be restored through renewal or other methods. All data will be cleared and become irrecoverable after deletion. Back up data in advance.
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, select Cluster, locate the target cluster, click More in the operation column, and select Terminate/Return from the drop-down list.
3. In the pop-up window for confirmation of the deletion, click Submit to delete the cluster completely.
Pay-as-you-go clusters can be deleted completely in the console.
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, choose Resource > Cluster, locate the target cluster, click More in the operation column, and select Terminate/Return from the drop-down list.
3. After confirming the deletion details, click Next, and click Delete in the pop-up window to delete the cluster.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan