[rabbitmq-discuss] Ready, Unacked and Total messages of Queues
juno at algorithmictradinggroup.com
Tue Apr 15 08:55:45 BST 2014
thanks very much MK
So it's good to hear that #ready msgs high is not impacting RabbitMQ
because we encountered an issues like the total messages in rabbit was up
to 300K, while some applications have queues of extremely high #ready, but
no #unack, while some applications have queues of high #unack, but no
thats helps me to troubleshoot which application I should look into.
On Tue, Apr 15, 2014 at 3:42 PM, Michael Klishin <mklishin at gopivotal.com>wrote:
> On 15 April 2014 at 11:37:39, Juno Chan (juno at algorithmictradinggroup.com)
> > > thanks very much. So, for the queues having high values in ready&
> > total # of messages(even go up to 300K messages), rabbit MQ performance
> > won't get affected?
> > only those queues having high values in unacked and total would
> > harm the rabbitMQ performance, is that correct?
> Unacknowledged messages are still kept around by RabbitMQ until they are
> or rejected, so it’s the total number of messages that really matters.
> > BTW, for 2 applications subscribing to the same subscribe channel,
> > 2 separate queues are created, if for some reasons, one of them
> > has problems and cause the queue stuck (e.g. high # unack messages)
> > will another queue being affected?
> A single queue can only use a single CPU core. The number of messages in
> the longest
> matter a lot less compared to how much disk I/O RabbitMQ has to do, either
> due to
> memory pressure or a high rate of messages published as persistent and
> routed to
> durable queues.
> Avoid overloaded queues as much as possible. See also
> Software Engineer, Pivotal/RabbitMQ
Algorithmic Trading Group (ATG) Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss