[rabbitmq-discuss] High-number of unack-ed messages

Matthew Sackman matthew at lshift.net
Thu May 13 16:28:11 BST 2010

On Thu, May 13, 2010 at 10:20:06AM -0500, Brendan Doyle wrote:
> On 1.7.2 I often see unack count reported by rabbitmqctl much higher than my QoS x number of consumers
> I always wrote it off to high throughput and different priorities on handling new incoming messages vs. acks or another internal implementation detail

Yeah, that's generally wise - in general the numbers reported by
rabbitmqctl can't be trusted too much as they're accurate only for
things that have *really* made it to the queue - there are plenty of
places within rabbitmq where buffering can occur.


More information about the rabbitmq-discuss mailing list