[rabbitmq-discuss] RabbitMQ timing out under small load

gfodor gfodor at gmail.com
Wed Jan 7 23:00:38 GMT 2009


Doing a little more log grepping revealed that the rate of timeouts on both
nodes during the incident are pretty much identical, so there wasn't a
timeout bias towards one node or the other according to the logs.

On node 1

 tail -n 100000 rabbit.log | grep -A2 -B2 timeout | grep '6-Jan-2009::02'  |
grep 'ERROR' | wc -l
15
root at rabbit1:/var/log/rabbitmq# tail -n 100000 rabbit.log | grep -A2 -B2
timeout | grep '6-Jan-2009::01'  | grep 'ERROR' | wc -l
69
root at rabbit1:/var/log/rabbitmq# tail -n 100000 rabbit.log | grep -A2 -B2
timeout | grep '6-Jan-2009::00'  | grep 'ERROR' | wc -l
21


On node 2

 tail -n 100000 rabbit.log | grep -A2 -B2 timeout | grep '6-Jan-2009::02'  |
grep 'ERROR' | wc -l
27
root at rabbit2:/var/log/rabbitmq# tail -n 100000 rabbit.log | grep -A2 -B2
timeout | grep '6-Jan-2009::01'  | grep 'ERROR' | wc -l
66
root at rabbit2:/var/log/rabbitmq# tail -n 100000 rabbit.log | grep -A2 -B2
timeout | grep '6-Jan-2009::00'  | grep 'ERROR' | wc -l
8


-- 
View this message in context: http://www.nabble.com/RabbitMQ-timing-out-under-small-load-tp21315520p21342362.html
Sent from the RabbitMQ mailing list archive at Nabble.com.





More information about the rabbitmq-discuss mailing list