[rabbitmq-discuss] OOM kill

Dmitry Andrianov dmitry.andrianov at alertme.com
Fri Mar 7 17:16:10 GMT 2014

We are trying to load-test RabbitMQ server in different configurations 
on Amazon EC2 node.
Most of our tests end with Linux OOM killer intervening and killing Rabbit.
That is something I cannot really understand especially given that it is 
reproducible even with vm_memory_high_watermark set to 0.2 and no other 
processes running on that box.
So if someone could shed some light onto that issue it would help a lot.

Below the status response not long before the process was killed:

      "Erlang R15B01 (erts-5.9.1) [source] [64-bit] [async-threads:30] 

Couple of strange things there are:

1. {vm_memory_limit,804643635} but still memory {total,1984625336}. How 
is that possible? https://www.rabbitmq.com/memory.html says that erlang 
process can take twice the configured size so I expected that but it is 
definitely more than twice.

2. {plugins,-44730984} - how this one is possible?

And just in cast it is needed, below is /proc/X/status

VmPeak:     2267580 kB
VmSize:     2110952 kB
VmLck:           0 kB
VmHWM:     2096276 kB
VmRSS:     2020848 kB
VmData:     2075168 kB
VmStk:          88 kB
VmExe:        1604 kB
VmLib:        4848 kB
VmPTE:        4304 kB
Threads:    31

Thanks in advance!

This email is for the use of the intended recipient(s) only.
If you have received this email in error, please notify the sender immediately and then delete it.
If you are not the intended recipient, you must not use, disclose or distribute this email without the
author's prior permission. AlertMe.com Ltd. is not responsible for any personal views expressed
in this message or any attachments that are those of the individual sender.

AlertMe.com Ltd, 30 Station Road, Cambridge, CB1 2RE, UK.
Registered in England, Company number 578 2908, VAT registration number GB 895 9914 42.

More information about the rabbitmq-discuss mailing list