Description of problem: When the director node runs out of physical memory, RabbitMQ shuts itself down due to running out of memory. eck has traced it to here : ERTS_ALC_INLINE void *erts_alloc_fnf(ErtsAlcType_t type, Uint size) { return (*erts_allctrs[ERTS_ALC_T2A(type)].alloc)( ERTS_ALC_T2N(type), erts_allctrs[ERTS_ALC_T2A(type)].extra, size); } Version-Release number of selected component (if applicable): ospd72 (RHN) How reproducible: 100% Steps to Reproduce: 1. OSPd w/ 8GB of RAM should cause this to happen with a small POC deployment Actual results: RabbitMQ-server stops Expected results: RabbitMQ-Server keep thumping
OOM will kill it anyway if the memory is low, and it's hard to handle it properly (both from technical, and from business logic PoVs). The proper way to "fix" that is to either adjust number of messages pushed into / read from RabbitMQ (it's not up to the bus to decide what message to store and what to discard to prevent OOM), or increase total size of physical memory available. I'm going to close this as NOTABUG.