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

Matthias Radestock matthias at rabbitmq.com
Thu May 13 18:40:47 BST 2010


Matthew Sackman wrote:
> 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.

What Matthew says is true, but the discrepancy you are seeing still 
strikes me as somewhat unusual. For the reported unacked message count 
to be much higher than the prefetch limit x number of consumers one of 
the following likely has happened:

a) the prefetch limit was only set after the consumer have been created

b) messages were consumed with basic.get rather than basic.consume

Is that the case? If not, could you post the code to reproduce the 
results you are seeing? There may be a completely innocent explanation, 
but there could also be a bug lurking somewhere, so I'd like to 
understand what is happening here.



More information about the rabbitmq-discuss mailing list