[rabbitmq-discuss] One node in a cluster never fully starts up

Francesco Mazzoli francesco at rabbitmq.com
Thu Jul 26 16:55:13 BST 2012

At Thu, 26 Jul 2012 08:45:50 -0700,
Matt Pietrek wrote:
> Francesco,
> Thanks for the quick reply. A couple of replies/questions:
> If I'm understanding what you're saying, we should be starting up our brokers
> sequentially. However, in my experience this hasn't worked. For instance,
> we've seen mq1 stall in its startup, waiting for mq3 to start.  But mq3 can't
> start (per the sequential logic) till mq1 finishes starting up. Per advice I
> received from you previously (below) we've moved to async startup of the
> brokers:
> http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-June/020689.html

Ah, I remember now!  Your problem is that you want to recover the nodes and you
don't know which is the last one going down, so some nodes stall.  And yes, in
that specific case I could not see any problems (and I still can't) with the
parallel startup *if you're not upgrading rabbit*.

That said, those mnesia messages are quite mysterious. Could you send the Rabbit
logs as well?

Francesco * Often in error, never in doubt

More information about the rabbitmq-discuss mailing list