[rabbitmq-discuss] Why rabbitmq stop pushing message to consumer
qiujixiong at 163.com
Mon Apr 28 03:38:52 BST 2014
Thanks for your response very much!
There indeed were some RAM alarms logged while no disk alarm. The RAM alarms were raised after message accumulate for a long time.
It should be the result, not the reason, right?(before the alarms raised, consumers could not receive message already)
What I can saw at that time was that all consumer threads could not receive message from rabbitmq and gdb tell me they were blocked in tcp receive function.
The connection usage currently is not very well and we will enhance it later. What I confused is the blocking of consumer(as you said, they should not be blocked). The reason is still uncertain.
At 2014-04-25 19:58:36,"Michael Klishin" <mklishin at gopivotal.com> wrote:
>Resource-based flow control should only block publishers. Re-creating connections
>won’t help: every publishing connection will be blocked. Consumers should not
>be blocked but nearly running out of disk space sounds alarming and can prevent
>RabbitMQ from moving messages to disk or very heavy OS paging .
>What’s in RabbitMQ log? There should be disk and RAM alarms logged. rabbitmqctl status
>indicates disk limit alarm should be on.
>Software Engineer, Pivotal/RabbitMQ
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss