[rabbitmq-discuss] RabbitMQ Startup/Stopping

Matthew Sackman matthew at rabbitmq.com
Tue Feb 22 10:26:43 GMT 2011

On Tue, Feb 22, 2011 at 03:47:02PM +0530, Sunil Arora wrote:
> We are using RabbitMQ 2.2.0 with erlang 5.7.2.
> > Regarding, does this follow it being shut down with a "kill"
> > rather than shutdown cleanly?
> Looking at the shutdown_log says "Stopping All nodes... OK done."
> Don't know how to trace if it was a case of force kill.

Mmm, ok. Upgrading to 2.3.1 will definitely add one optimisation which
has the capacity to vastly reduce the amount of disk activity (if that
is indeed what's going on), but it's not clear whether that would apply
in your case.

Basically, Rabbit doesn't always write all data to disk immediately.
Consequently on shutdown, it can have a fair backlog to write out. This
can take some time. If you force kill it during this time, then on
startup, it has to do all sorts of consistency checks (the equiv. of an
fsck) which will take even longer. So whilst it may take 5 mins to shut
it down, it's by far the better idea to allow it to do that so that the
startup is then near instantaneous.

The optimisation mentioned above allows the elimination of disk activity
for queues that have been deleted. If Rabbit is heavily loaded, the part
of Rabbit that writes messages to disk can be some way behind the
various queues, and as such can still continue to write out messages for
queues that have since been deleted. We added an optimisation that
allows the detection of this situation and thus the elimination of these
writes. This may help you if this corresponds to your situation.


More information about the rabbitmq-discuss mailing list