[rabbitmq-discuss] Miscellaneous Question

[Jason J. W. Williams]

Regarding the Mnesia issue attached is the ERL crash dump and below is
the output of starting Rabbit:

RabbitMQ 1.5.0 (AMQP 8-0)
Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies
LLC., and Rabbit Technologies Ltd.
Licensed under the MPL.  See http://www.rabbitmq.com/

Logging to "/var/log/rabbitmq/phantome-rabbit1.log"
SASL logging to "/var/log/rabbitmq/phantome-rabbit1-sasl.log"

starting database             ...{"init terminating in
do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{{timeout_waiting_for_tables,[user,user_vhost,vhost,rabbit_config,listener,durable_routes,route,reverse_route,durable_exchanges,exchange,durable_queues,amqqueue]},{rabbit,start,[normal,[]]}}}}},[{init,start_it,1},{init,start_em,1}]}}



On Wed, Jan 14, 2009 at 3:17 PM, Jason J. W. Williams
<jasonjwwilliams at gmail.com> wrote:
> Hello,
>
> A few miscellaneous questions came to me last night, so I thought I'd
> bundle them into one e-mail. Any insight is greatly appreciated.
>
> * How does one monitor memory consumption by a queue?
>
> * If messages persist to disk do they relieve memory pressure on the queue?
>
> * How resilient is the Mnesia DB to sudden death of the process using it?
>
> The last question has to do with me trying to start Rabbit again
> yesterday and it hanging on start and then issuing an error about
> reading the databases. Clearing the Mnesia files in /var/lib/rabbitmq
> allowed Rabbit to start...but I assume in a production scenario this
> would have eliminated any durable queues/exchanges and persistent
> messages.
>
> Just concerned that the Mnesia DB is fragile and susceptible to
> corruption when Rabbit is kill -9'd.
>
> -J
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: erl_crash.dump
Type: application/octet-stream
Size: 484805 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090114/da9706e3/attachment.obj