- Release Notes and Announcements
- Release Notes
- Announcements
- Notice on Disabling the Automatic Group Creation for Some Virtual Clusters in TDMQ for RocketMQ 4.x
- Notice on the Cessation of Purchase for TDMQ RocketMQ 4.x Virtual Clusters Switching Cluster Billing Modes
- Commercial Launch of TDMQ for RocketMQ Exclusive Cluster
- TDMQ for RocketMQ Beta Test to Be Ended
- TDMQ for RocketMQ Beta Test Start
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Practical Tutorial
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ for RocketMQ Service Level Agreement
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Notice on Disabling the Automatic Group Creation for Some Virtual Clusters in TDMQ for RocketMQ 4.x
- Notice on the Cessation of Purchase for TDMQ RocketMQ 4.x Virtual Clusters Switching Cluster Billing Modes
- Commercial Launch of TDMQ for RocketMQ Exclusive Cluster
- TDMQ for RocketMQ Beta Test to Be Ended
- TDMQ for RocketMQ Beta Test Start
- Product Introduction
- Purchase Guide
- RocketMQ 5.x
- RocketMQ 4.x
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Development Guide
- Practical Tutorial
- SDK Documentation
- Migration to Cloud
- API Documentation
- FAQs
- TDMQ for RocketMQ Service Level Agreement
- Contact Us
TDMQ for RocketMQ provides two consumption modes: Push and Pull. The Push mode is implemented based on the Pull mode, wrapping a layer on the Pull mode. It is a variant of the Pull mode rather than a true Push mode.
Therefore, it can be considered that the TDMQ for RocketMQ SDK continuously performs message pulling tasks. Below are the possible results of each pull:
After the SDK successfully pulls messages, if some messages are filtered out (such as by tag), it will put the message pulling request to the blocking queue to pull messages in a loop; otherwise, the messages will be put to the consumer for consumption while the message pulling request will be put to the blocking queue.
If no new messages are available in the broker or no messages are matched,
pullRequest will be put to the blocking queue to continue to pull messages in a loop.That is to say, as long as the consumer is online, it will initiate requests to the server periodically even if no messages are produced. This can ensure the timeliness of message consumption. If you want to reduce the number of pulls, refer to the following section.
How to Control Pulling Frequency
In the Pull mode, you can actively control the message pulling frequency of consumers by using throttling components or waiting for a desired period of time before the next pull.
In the Push mode, you can use
PullInterval to set the message pulling interval for consumers.// Set the interval to 60spushConsumer.setPullInterval(60 * 1000);
Note
Modifying the message pulling interval may cause a higher consumption delay. Therefore, proceed with caution.
If a small number of messages are produced, the long polling time of fixed 15s will be readily reached; that is, a broker will initiate at least four pulls for a queue per minute. If there are 10 topics with 3 queues each, and there are 2 brokers on the server, the number of pulls will be 240 (1032*4). In this case, four pulls are initiated per second.
In actual scenarios, retry topics may be generated during the production and consumption processes. As the retry queue also needs to be pulled, the message pulling frequency will increase.
Yes
No
Was this page helpful?