[rabbitmq-discuss] RabbitMQ timing out under small load

Dmitriy Samovskiy dmitriy.samovskiy at cohesiveft.com
Wed Jan 7 22:26:57 GMT 2009

>> Are you sure there is nothing of interest in rabbit logs, apart from
>> timeouts, on both 
>> instances? Maybe something in system logs?
>> Any info in client logs maybe that could explain why all of them connected
>> to a single 
>> broker (I assume normally you spread connections somewhat equally between
>> the 2 brokers)?
> I took another look at the logs and really there is nothing interesting
> other than a series of timeout errors as pasted in my original post. Any
> other ideas? 
Do you see timeouts in rabbit.log on the instance which had many connections during the 
incident, on the instance which had almost no connections during the incident, or on both?

How many connections does each broker have right now?

Essentially, I think we can get some useful insight into the problem if we understand why 
one node during the incident had no connections and another had all of them (provided this 
is not how you guys usually run it).

Also, to confirm info from your original report: you saw the problem was resolved when you 
attached a consumer to 2 non-important queues and drained them by consuming all messages 
from them. Did you do it on the node with connections or node without connections, and on 
which nodes did those queues live?

I know I keep asking basically same things over and over again, just shooting in the dark 
here :)

More information about the rabbitmq-discuss mailing list