[rabbitmq-discuss] Memory limit cleanup, hanging connections.

[Irmo Manie]

On Mon, Oct 15, 2012 at 12:44 PM, Simon MacMullen <simon at rabbitmq.com>wrote:

> Yes, that's absolutely correct. The blocked connections don't perform any
> network operations at all - which means that not only don't they check for
> heartbeats, they don't even detect the TCP connection being torn down. As
> soon as the memory alarm clears, the connections will unblock, notice the
> TCP connection having gone away, and vanish.
>
>
Ok, good to know. I reckon the connections themselves don't take that much
resources or keep hold of memory consuming parts? That it's purely the
queues and their messages eating the memory?


> If you've "filled up" all your queues then they will have been paging to
> disc for some time - cleaning all that up can be quite slow.
>
>
Any reason why this is that slow? Does it look up every message 1 by 1 in
the storage or something?

Cheers,
- Irmo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121015/7c5b75cf/attachment.htm>