[rabbitmq-discuss] Erlang crashes trying to allocate 583848200 bytes of memory

Dom54 D.Rotondi at Computer.Org
Tue Jan 25 11:44:17 GMT 2011

On Jan 25, 11:44 am, Matthias Radestock <matth... at rabbitmq.com> wrote:
Hi Matthias,
> Dom,
> Dom54 wrote:
> > To our understanding the RabbitMQ broker (and its supporting
> > Erlang environment) keeps to be delivered messages in memory; if the
> > consumer is not fast enough the Erlang memory footprint grows till the
> > broker crash.
> The rabbit code does not hold on to messages in memory when it has
> delivered them to consumers and it is under memory pressure.

Thats what I stated above. In memory seems to be buffered only
messages that have not been delivered.

> But we do rely on the underlying erlang network stack and O/S to tell us
> when it can't send messages to the consumers. Rather than, say, blindly
> buffering them. It's possible that therein lies the problem on Windows.
> Btw, when you tweaked the vm_memory_high_watermark settings, did you
> check that they were actually taking effect? There is a message near the
> beginning of the rabbit log file indicating how much memory it is trying
> to limit itself to.

Yes we checked the tweak effect in the log file and the log file
reflects the setting.
BTW we have just completed another test using a Windows Server 2008 R2
64 bit version on a vM with 4 BG RAM, and the problem is still there.
We are now trying using the last Erlang release (R14B01) instead of
the R13B03 included in the RabbitMQ distribution, hoping this release
has fixed some of the problems.
Thanks, ciao

> Regards,
> Matthias.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list