[rabbitmq-discuss] RabbitMQ very slow (or never) shuts down

[Matt Pietrek]

Thanks for the confirmation Tim.

> Please make sure you plan your upgrade carefully as there are breaking
changes between the 2.8.x series and 3.0.0.

Oh yeah. I'm very aware of that. That's one reason we haven't jumped to 3.0
already. I've already got time allotted for reworking our tooling to work
with the new 3.0 goodness.


On Mon, Dec 10, 2012 at 11:12 AM, Tim Watson <tim at rabbitmq.com> wrote:

> Hi Matt,
>
> On 10 Dec 2012, at 19:00, Matt Pietrek wrote:
>
> > Quick follow up on this - Was this bug fix implemented in 2.8.7 or
> something later, i.e. 3.0?
> >
>
> According to the bug tracker, the fix for this was included in the 3.0.0
> release.
>
> > I think I'm running into this again when shutting down a set of
> bi-directionally federated brokers. It appears when a broker shuts down, it
> wants to reach over to the other broker to clean up something (federation
> queue?)
> >
> > If the other broker has already shut down, the currently shutting-down
> broker will stall for a very long time (e.g. 15 minutes or more.)
> >
>
> Yeah that sounds like the canonical scenario. You will need to plan an
> upgrade to 3.0.0 to see the benefits of this fix I'm afraid. Please make
> sure you plan your upgrade carefully as there are breaking changes between
> the 2.8.x series and 3.0.0.
>
> Cheers,
> Tim
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121210/373fce4b/attachment.htm>