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

Querying Retry Messages

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-01-23 17:34:04
To ensure message lifecycle integrity in scenarios where business processing or message consumption fails, TDMQ for RocketMQ supports a retry mechanism after consumption failures.
For TDMQ for RocketMQ 4.x clusters, the number of message retries set on the client prevails.
For TDMQ for RocketMQ 5.x clusters, you can set the number of message retries when a group is created. If you use a 5.x client, the number of retries set on the server prevails. If you use a 4.x client, the number of retries set on the client prevails.

Scenarios

To check whether retry messages exist under a specific topic, you can query messages on the Retry Message Query page. You can expand the details to view information such as the time of each retry and the producer's IP address. In addition, you can export messages and view message details.

Operation Steps

1. Log in to the TDMQ for RocketMQ console, and click Retry Message Query in the left sidebar.
2. On the message query page, select a region and enter the query conditions as prompted.
Cluster: Select the cluster where the topic to be queried is located.
Topic: Select the topic to be queried.
Group: To query retry messages under a 5.x cluster, select the specific group subscribed to under this topic. This field is not required for 4.x clusters.
Time Range: Select the time range within which you want to query messages. The options include the last 30 minutes, last 1 hour, last 6 hours, last 24 hours, last 3 days, and a custom time range.
Query Methods: The message query feature supports the following query methods:
Query all: applies when the information about retry messages is unclear, and is used to query all retry messages under the current topic.
By message ID: This is a precise query method, with quick speed and accurate matching.
By message key: This is a fuzzy query method suitable for scenarios where you have not recorded the message ID but have set a message key.
Note:
To ensure the query speed, the server queries the most recent messages in chronological order when you select Query all. However, due to query time and display limitations, messages that need to be troubleshooted may not be located quickly. It is recommended that you use more specific query conditions, such as the message ID and message key.
3. Click Query. The list at the bottom of the page displays all query results with pagination.
4. After the query is completed, you can click a single message to view its retry status, such as the number of retries and the producer's IP address. You may also click Other Operations in the operation column to view message details and trace information.


ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック