[rabbitmq-discuss] rabbitmq-discuss Digest, Vol 18, Issue 34

[Edwin Fine]

Ilya,

Are you using Linux? If so, did the Linux OOM killer maybe zap the Erlang
node?

You could try this:

$ sudo sysctl vm.overcommit_memory=2
vm.overcommit_memory = 2

Also take a look at overcommit_ratio and swappiness.

HTH.
Ed

On Mon, Nov 17, 2008 at 5:53 PM, Ilya Grigorik <ilya at aiderss.com> wrote:

> I've been running more benchmarks on Rabbit today, few more questions
> popped up:
>
> Any rules of thumb for memory requirements on Rabbit? I've setup a simple
> consumer which pushes ~10kb/s into a Rabbit queue, and the persister file is
> growing at an expected rate, but the memory appears to be fluctuating all
> over the map. My persister got up to 386MB, but resident side of rabbit shot
> up to 3.5GB.
>
> Also, I've added a liberal swap partition to the box, but I'm still seeing
> same behavior as before: rabbit died at around 2.2GB in the perister.log.
> Kernel logs are not showing anything suspicious, and the node doesn't spit
> out anything useful either:
>
> =INFO REPORT==== 17-Nov-2008::17:46:00 ===
>     alarm_handler: {clear,system_memory_high_watermark}
>
> =INFO REPORT==== 17-Nov-2008::17:46:26 ===
> Rolling persister log to
> "/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG.previous"
>
> ---
>
> Erlang has closed
> /usr/local/lib/erlang/lib/os_mon-2.1.8/priv/bin/memsup: Erlang has closed.
>
> Is there a debug mode I could enable?
>
> ig
>
> P.S. I'm in for pitching in to fix this stuff. ;-)
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20081117/1c11fedd/attachment.htm