Thanks for the additional information. I'll have another go at
On 27/02/12 19:34, Chip Salzenberg wrote:

Our local Erlang expert is on vacation, but he rescued our cluster.
He described a mailbox full of messages that some process was not
consuming. When he killed the process and, IIRC, the "shell" that had
spawned it (I am merely parroting what I recall, this may be the wrong
term), the bloat was cured and memory usage returned to normal.
I don't suppose you have any record of what type of process it was /
what the messages looked like?

Cheers, Simon
Details that might matter in reproduction: Our troubled mirrored
queue used mode "nodes" (not "all"), picking two nodes out of a
cluster of four. When I created it, I used a modified rabbitmqadmin
that connected to one of the two nodes, and specified that it and one
other node should mirror the queue. All messages were written with
delivery-mode 2. Messages are about 46K each. While some of the
messages were consumed, most were purged. Queue deletion did not cure
the leak.
rabbitmq-discuss mailing list
rabbitmq-discuss at

Simon MacMullen
RabbitMQ, VMware

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 8 of 11 | next ›
Discussion Overview
grouprabbitmq-discuss @
postedFeb 22, '12 at 8:12p
activeMar 12, '12 at 5:08p



site design / logo © 2022 Grokbase