- 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
This document describes the dead letter queue in TDMQ for RocketMQ and how to use it.
Feature Description
When a message is consumed for the first time by a consumer and does not receive a normal response, or when users request the server to deliver it again, TDMQ for RocketMQ will automatically attempt to deliver this message again through the message retry mechanism until it is consumed successfully. When the number of retries reaches the specified value but the message is still not consumed successfully, retry will stop, and the message will be delivered to the dead letter queue.
If messages enter the dead letter queue, TDMQ for RocketMQ can no longer automatically process them. In this situation, human intervention is required. You can confirm it via message export, or via specified message resending on the control console.
Feature Description
Different from the retry queue, which supports automatic consumption, messages within the dead letter queue require manual intervention.
The validity of messages also adheres to the rule of deletion after three days by default.
The dead letter queue starts with
%DLQ% and corresponds to the consumer group one by one. Therefore, a dead letter queue contains all dead letter messages corresponding to the group ID, regardless of their originating topic.
Yes
No
Was this page helpful?