[rabbitmq-discuss] Connection blocked by "flow" for more than 600 seconds

Choo e34_520 at yahoo.com
Fri Oct 11 03:22:32 BST 2013

Hi Simon,

As memory is plenty, I found that file descriptors hit the default limit,
so, I bumped the limit up to 5,120, and finally to 10,240 on each nodes.  It
turned out that the file descriptors also touched the limit (around 10,086),
and things started to go downhill.


I started processes in reverse order, by starting subscriber-side first
(1:42), then the bigger publishers later (1:45).  The number of published
messages bounced up&down, then just after 1:48, the most of the publishers
were blocked.

There are more than 350 of blocked connections like below now (and file
descriptors are running at 7,558 + 4,647 on 2 nodes): ->	blocked	1261.558817	flow ->	blocked	1326.324919	flow ->	blocked	1326.45322	flow ->	blocked	1278.581221	flow ->	blocked	1312.584426	flow ->	blocked	1279.623625	flow ->	blocked	1294.492535	flow ->	blocked	1276.134377	flow ->	blocked	1292.862081	flow ->	blocked	1290.695249	flow ->	blocked	1255.599642	flow ->	blocked	1284.984752	flow

Please kindly suggest.

Thank you and Best Regards,

View this message in context: http://rabbitmq.1065348.n5.nabble.com/Connection-blocked-by-flow-for-more-than-600-seconds-tp30349p30402.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list