3 ms·
The RabbitMQ stuff seems pretty straightforward: Channel prefetch: https://www.rabbitmq.com/confirms.html https://www.rabbitmq.com/confirms.html "Once the nu
by mannyv 4y ago
The RabbitMQ stuff seems pretty straightforward:
Channel prefetch:
https://www.rabbitmq.com/confirms.html https://www.rabbitmq.com/confirms.html
"Once the number reaches the configured count, RabbitMQ will stop delivering more messages on the channel unless at least one of the outstanding ones is acknowledged"
consumer prefetch:
https://www.rabbitmq.com/consumer-prefetch.html https://www.rabbitmq.com/consumer-prefetch.html
So a prefetch count of 1 = 1 un-ACKed message -> what they want
- eternalban 4y agoThe article unintentionally communicated more about the engineering team than the subject. btw, publisher confirms used in conjunction with prefetch setting can allow for flow control within a very well behaved band. People run into issues with Rabbit for two reasons. You noted one (they are documentation averse), and number is two is mistaking a message queue for a distributed log. Rabbit does -not- like holding on to messages. Performance will crater if you treat it as a lake. It is a river
- baq 4y agogreat point and same is true for postgres! where I'm at DBAs rip people's legs off for idle in transaction over a few seconds