[rabbitmq-discuss] rabbitmqctl stall/hang when leaving a cluster

[Matt Pietrek]

| So how long are you waiting when determining it's hanging? Less than 30
seconds?

Just to be double sure, I let it sit for an hour yesterday. I would have
expected a timeout, but it never came.

It's a pretty easy scenario to script and try out. I'd send you my code,
but it relies on other internal commands.

There may also be a timing issue. If I put a 10 second delay after
restarting one broker, and before stopping the next, it seems to help.

That is:

for x in broker_list:
    stop x
    start x
    sleep(10)

Matt

On Fri, Feb 24, 2012 at 4:22 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 23/02/12 21:00, Matt Pietrek wrote:
>
>> The nohup.out on the failing node ends with:
>>
>
> <snip>
>
>  starting database                                                     ...
>>
>
> So how long are you waiting when determining it's hanging? Less than 30
> seconds?
>
> Because that looks like Rabbit is waiting for another cluster node (if it
> was not the last to shut down, but is the first to start up, it will wait
> for the one that was the last to shut down. But it will only wait for 30
> seconds before spitting out an error. I'm not sure how else you could get
> it to stop there *without* any further output though.
>
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120224/11ea4200/attachment.htm>