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

Resetting the Consumption Offset

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-23 17:34:04
A consumer offset represents the position of a message consumed by a consumer. In certain business scenarios, such as data processing exceptions, business logic changes, or system Ops requirements, the consumer offset may need to be reset to consume specific messages again or skip them.

Constraints and Limitations

TDMQ for RocketMQ supports resetting a consumer offset for offline groups. However, this feature is only supported for consumer groups in push consumption mode; otherwise, the resetting will fail.

Operation Steps

1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, choose Resource > Cluster, select a region, and click the ID of the target cluster to go to the cluster basic information page.
3. On the cluster basic information page, select the Group tab.
5.x clusters: Click Reset Offset in the operation column of the target group.

4.x clusters: Click Reset Offset or Reset the retry queue offset in the operation column of the target group.

The following table describes Reset Retry Queue Offset.
Feature
4.x Cluster
5.x Cluster
Retry queue granularity
Retry queues are created by group.
A group only has one retry queue, and all failed messages from all topics it subscribes to are sent to the retry queue.
Retry queues are created by group and topic.
A group has a dedicated retry queue for each topic it subscribes to.
Impact of resetting classic queues
Resetting the consumer offset of a topic does not automatically reset the retry queue.
Resetting the consumer offset of a topic will automatically reset the offset of the dedicated retry queue.
Reasons for this design
This design avoids mutual impact.
If a group subscribes to Topic A and Topic B, and the shared retry queue is reset when the offset for Topic A is reset, the failed messages of Topic B are affected.
Retry queues of different topics are isolated from each other.
Each topic has its own independent retry queue. When Topic A is reset, only the retry queue of Topic A is affected. The retry queue of Topic B is not affected. Therefore, the consumption process can be reset automatically.
Additional feature
An independent feature for resetting the retry queue offset is provided. To clear all failed messages, you can perform this operation separately.
No additional features are needed because the reset queue offset is automatically reset when a topic is reset.
4. In the pop-up window, you can select whether to set the consumption offset of a topic Start from the latest offset or Start from specified time point (that is, specifying the position from which consumers start consuming messages under this subscription).
If you select to reset the offset from the latest offset, all backlogged messages of the group in the specified topic will be cleared. Proceed with caution.



5. Click Submit to complete the settings.




Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan