GenerousMan opened a new issue, #7772: URL: https://github.com/apache/rocketmq/issues/7772
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary Current RocketMQ supports POP consumption feature, but this introduces a problem—when clients continuously pop messages, messages that time out on ACK enter the Retry Topic, leading to periodic redelivery. In extreme cases, if the client never sends an ACK, the cluster traffic will continue to rise. This issue can be catastrophic under certain circumstances: the accumulation of messages keeps growing, and once consumers are unable to match the required consumption capacity, slow ACKs seem inevitable, leading to increasingly severe consumption delays. Therefore, we need to impose limits on the number of inflight messages. When the number of inflight messages for each queue reaches a certain threshold, we will cease pushing messages from that queue, ensuring a relatively stable amount of messages awaiting ACK for each queue—of course, these functions require the addition of switches and threshold limits in the brokerConfig to control them. ### Motivation Ensuring broker protection capabilities when POP does not return ACK ### Describe the Solution You'd Like add a inflight messages' num limitation. ### Describe Alternatives You've Considered null ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
