On 11/24/21 12:34 AM, DHilsbos@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 [0][1], if configuring rabbitmq cluster by pacemaker.
[0] https://www.rabbitmq.com/pacemaker.html#auto-pacemaker
[1] https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/rabbitm...
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@PerformAir.com www.PerformAir.com