[rabbitmq-discuss] Proper protocol for dealing with crash dumps?

Alex Zepeda alex at inferiorhumanorgans.com
Sun Oct 7 06:18:13 BST 2012

On 10/3/12 2:24 PM, Matthias Radestock wrote:

> R13B03 is ancient, and countless bugs have been fixed since then,
> including memory leaks. Though, tbh, it's not the first place I'd look.
> Rabbit 2.8.7 plugs some leaks, but they were confined to HA queues (see
> the release notes for more details), so unless you are using those then
> upgrading won't help.
> Have you changed the memory watermark settings of rabbit at all? If not
> then rabbit really shouldn't run out of memory unless another program is
> stealing the memory, or your app is creating lots of exchanges, queues
> or bindings. Or lots of connections. Or you are using some exotic
> plug-ins with hitherto undiscovered bugs. In all those cases, grabbing
> the output of 'rabbitmqctl report' before rabbit dies should offer some
> clues.

The config changes are, I think, limited to shovel related items,
logging, disk space, and TCP bits.  These machines have under 2GB of RAM
so allocating in excess of 700MB seems a bit odd.

In an ideal world we'd see around 48,000 messages per day *at the very
most*.  In practice, we're running into problems where an order of
magnitude more messages are being queued up under some circumstances...
but I'd expect that rabbit should handle that gracefully and block the
connection, no?

- alex

More information about the rabbitmq-discuss mailing list