[rabbitmq-discuss] RabbitMQ crashed in ets:insert_new - looks like a genuine bug...

Eugene Kirpichov ekirpichov at gmail.com
Fri Aug 12 02:23:36 BST 2011

A lot of clients (a thousand or more) were rapidly publishing 1kb
messages to a queue, and then rabbitmq crashed.

In fact I had a cluster of 4 rabbits, and 2 of them crashed as a
result. The remaining 2 continued working ok.

Here's a crash report from rabbit-sasl.log. I do not give the full log
because it's large, contains message data (which my employer might not
like) and I'm too lazy to automatically snip it.
But the log is really full of things exactly like what I show. This
exact message gets repeated many times in the same second, and then it
finally crashed.

What other information can I provide to resolve this? Could this be an
error on my, not rabbit's, part? Having a sudden rabbitmq crash is not
really what I'd like to have in production :-|

=CRASH REPORT==== 11-Aug-2011::17:56:19 ===
    initial call: gen:init_it/6
    pid: <0.16624.0>
    registered_name: []
    exception exit: {badarg,

                                       <<....>>, % (snipped)
                                       [<<....>>]}, % (snipped too)
      in function  gen_server2:terminate/3
    ancestors: [rabbit_amqqueue_sup,rabbit_sup,<0.137.0>]
    messages: [{'$gen_cast',{ack,none,[46689],<0.16623.0>}},
    links: [<0.263.0>]
    dictionary: [{fhc_age_tree,{0,nil}},
    trap_exit: true
    status: running
    heap_size: 1682835
    stack_size: 24
    reductions: 1260360700

Eugene Kirpichov
Principal Engineer, Mirantis Inc. http://www.mirantis.com/
Editor, http://fprog.ru/

More information about the rabbitmq-discuss mailing list