[openstack-dev] [Fuel] Rabbitmq 3.4.0 upgrade for the 6.1 release, is it worth it?

Dina Belova dbelova at mirantis.com
Wed Apr 29 08:46:11 UTC 2015


actually we do not insist this should b done for the MOS 6.1. That was the
question to the audience if someone is having other idea. All these
discussions have roots in the bug
https://bugs.launchpad.net/fuel/+bug/1447619 - we have found the issue with
RabbitMQ cluster behaviour under the networking load and Bogdan, Alexei
Khivin and Alex Nevenchannyy found that it possibly might be fixed
upgrading the RabbitMQ (trying it now). And actually this RabbitMQ release
contains lots of crucial bug fixes even without mentioned by Bogdan.

For 6.1 the found workaround might be used, section in the docs written,
etc. The question to the company is if that will be enough and what are we
going to do with it in future.


On Wed, Apr 29, 2015 at 11:24 AM, Alexei Sheplyakov <
asheplyakov at mirantis.com> wrote:

> Hi,
> Given that
> - MOS 6.1 should be released in a few weeks
> - rabbitmq is kind of a heart of OpenStack
> upgrading rabbitmq in MOS 6.1 seems to be an extremely bad idea.
> There will be always some bugs (both known and unknown), but we can't keep
> updating various
> components forever and should stop at some moment (which is presumably
> called `soft code freeze').
> Best regards,
>       Alexei
> On Wed, Apr 29, 2015 at 11:04 AM, Bogdan Dobrelya <bdobrelia at mirantis.com>
> wrote:
>> Hello.
>> There are several concerns why we have to upgrade RabbitMQ to 3.4.0 [0]:
>> 1) At least two bugfixes related to the current high-load issue with MQ
>> [1]:
>> - 26404 prevent queue synchronisation from hanging if there is a very
>> short partition just as it starts (since 3.1.0)
>> - 26368 prevent autoheal from hanging when loser shuts down before the
>> winner  learns it is the winner (since 3.1.0)
>> 2) We should as well check how the new 'pause-if-all-down' option works
>> for split brain recovery.
>> 3) We should address the 'force_boot' recommendations from this mail
>> thread [2] to speed up the MQ cluster assemble time.
>> The question is - is it worth it to do this in the 6.1 release scope?
>> I vote to postpone this for the 7.0 dev cycle as the impact of such
>> changes might be unpredictable.
>> [0] https://www.rabbitmq.com/release-notes/README-3.4.0.txt
>> [1] https://bugs.launchpad.net/fuel/+bug/1447619
>> [2]
>> http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg51625.html
>> --
>> Best regards,
>> Bogdan Dobrelya,
>> Skype #bogdando_at_yahoo.com
>> Irc #bogdando


Best regards,

Dina Belova

Software Engineer

Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150429/0158fb8f/attachment.html>

More information about the OpenStack-dev mailing list