[ops] [kolla] RabbitMQ High Availability
arnaud.morin at gmail.com
Wed Dec 1 20:02:02 UTC 2021
I definitely recommend upgrading to 3.8.
Also enable the durable queues.
This helped us a lot in managing our clusters.
We also applied the policy, which was originally taken from openstack ansible .
We also collect unroutable messages and send alerts based in that (but we had no issue recently thanks to all above).
Finally we ping all our clients using oslo_ping_endpoint  every five minutes so we know when an agent is disconnected.
Dunno about kolla, sorry.
Le 1 décembre 2021 19:15:41 GMT+01:00, "Braden, Albert" <abraden at verisign.com> a écrit :
>I read this with great interest because we are seeing this issue. Questions:
>1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x?
>2. Document  recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like?
>3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into?
>Does anyone have a sample set of RMQ config files that they can share?
>It looks like my Outlook has ruined the link; reposting:
>From: Arnaud Morin <arnaud.morin at gmail.com>
>Sent: Monday, November 29, 2021 2:04 PM
>To: Bogdan Dobrelya <bdobreli at redhat.com>
>Cc: DHilsbos at performair.com; openstack-discuss at lists.openstack.org
>Subject: [EXTERNAL] Re: [ops]RabbitMQ High Availability
>Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>After a talk on this ml (which starts at ), we endup building a
>documentation with Large Scale group.
>The doc is accessible at .
>Hope this will help.
>On 24.11.21 - 11:31, Bogdan Dobrelya wrote:
>> On 11/24/21 12:34 AM, DHilsbos at performair.com wrote:
>> > All;
>> > In the time I've been part of this mailing list, the subject of RabbitMQ high availability has come up several times, and each time specific recommendations for both Rabbit and Open Stack are provided. I remember it being an A or B kind of recommendation (i.e. configure Rabbit like A1, and Open Stack like A2, OR configure Rabbit like B1, and Open Stack like B2).
>> There is no special recommendations for rabbitmq setup for openstack,
>> but probably a few, like instead of putting it behind a haproxy, or the
>> like, list the rabbit cluster nodes in the oslo messaging config
>> settings directly. Also, it seems that durable queues makes a very
>> little sense for highly ephemeral RPC calls, just by design. I would
>> also add that the raft quorum queues feature of rabbitmq >=3.18 does
>> neither fit well into the oslo messaging design for RPC calls.
>> A discussable and highly opinionated thing is also configuring
>> ha/mirror queue policy params for queues used for RPC calls vs
>> broad-casted notifications.
>> And my biased personal humble recommendation is: use the upstream OCF RA
>> , if configuring rabbitmq cluster by pacemaker.
>>  https://secure-web.cisco.com/1N1wD9gW7NZho0LdTVNuiU2ZIB7NW-eJMfDgVzBH3D3E6URzGYPKa-uhcLHxy3tRvRXopjnLAd2CECD1urJyRpg8NBSxTOEUSPxOlS0cQyULtSQuDbVWr-W7Bl3ZRcdWPrF9EuX_b40IM7zTjqS40gImsEouTqtD1vlCuEoaFgpptDEuMuaNTqBJ0IAtiZHuWiW6E7ufTtgxmVbkGLjXCZw5ZNhibbu-kGVyA-7MQsxQ-RBgSq5peTcLBR2Vx-f9k/https%3A%2F%2Fwww.rabbitmq.com%2Fpacemaker.html%23auto-pacemaker
>> > Unfortunately, I can't find the previous threads on this topic.
>> > Does anyone have this information, that they would care to share with me?
>> > Thank you,
>> > Dominic L. Hilsbos, MBA
>> > Vice President - Information Technology
>> > Perform Air International Inc.
>> > DHilsbos at PerformAir.com
>> > www.PerformAir.com
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss