[rabbitmq-discuss] Erlang has closed?

Wed May 19 16:06:23 BST 2010

On Wed, May 19, 2010 at 10:55 AM, Matthew Sackman <matthew at lshift.net> wrote:
> On Wed, May 19, 2010 at 10:45:19AM -0400, tyler at echonest.com wrote:
>> The server process does get busy, up to about 80% of the available cpu.
>> It uses all of the available memory, and crashes shortly after. (Shouldn't
>> it be pinning the queues to disk automatically, or do i need to use 21444
>> for that...?)
>
> The new persister will gently push messages to disk when memory gets
> tight. That is not the behaviour of default branch or any released
> version of Rabbit.
>
>> The server never recovers, even if I kill all producers and most
>> consumers,  although the beam.smp process hangs on to all
>> the memory. I'm playing with 21444 now to see if i can replicate this.
>
> 21444 is ancient and should not be used. If you want to use the new
> persister, the correct branch is bug21673.
>
> Matthew
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

Ah ok, good to know. Based on this:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2009-October/005041.html
I thought 21444 might still be the best option for automatically
pinning large queues to disk, but I'll give 21673 a try today.

Looking closer at the logs for our production rabbit server, which
*is* still running 21444, i see that it died with the following
messages:

=INFO REPORT==== 17-May-2010::14:24:30 ===
    application: rabbit
    exited: {{timeout_waiting_for_tables,[rabbit_disk_queue]},
             {rabbit,start,[normal,[]]}}
    type: temporary

=ERROR REPORT==== 17-May-2010::14:24:30 ===
Error in process <0.100.0> on node 'rabbit at echonest03' with exit
value: {badarg,[{ets,insert,[rabbit_disk_queue,[{dq_msg_loc,{{resource,<<1
byte>>,queue,<<9 bytes>>},553567},false,true,<<16
bytes>>},{dq_msg_loc,{{resource,<<1 byte>>,queue,<<18
bytes>>},563611},false,true,<<16 bytes>>},{dq_msg_loc,{{resource,<<1
byte>>,queue,<<18 bytes>>},80964},false,true,<<16
bytes>>},{dq_msg_loc,{{resource,<<1 byte>>,queue...

=INFO REPORT==== 17-May-2010::14:24:33 ===
    application: mnesia
    exited: stopped
    type: temporary

=INFO REPORT==== 17-May-2010::14:24:33 ===
    application: os_mon
    exited: stopped
    type: temporary

Can you shed any light on this error?

thanks again,

--tyler