问题描述
如果我用 x-max-length 声明一个队列，一旦达到限制，所有消息都将被丢弃或死信.
If I declare a queue with x-max-length, all messages will be dropped or dead-lettered once the limit is reached.
我想知道 RabbitMQ 是否可以像 一样激活流量控制机制，而不是丢弃或死信内存/磁盘水印.原因是因为我想保留消息顺序(提交时；FIFO 行为)并且会更方便地减慢生产者的速度.
I'm wondering if instead of dropped or dead-lettered, RabbitMQ could activate the Flow Control mechanism like the Memory/Disk watermarks. The reason is because I want to preserve the message order (when submitting; FIFO behaviour) and would be much more convenient slowing down the producers.
推荐答案
rabbitmq-server github repo.我建议您在那里表达您的兴趣:
There are two open issues related to this topic on the rabbitmq-server github repo. I recommended expressing your interest there:
这篇关于带流量控制的RabbitMQ队列长度限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！