hi, I totally agree that you should target using quorum queues. You may also want to use stream queues and queue consistent naming, ending with a config like this: [oslo_messaging_rabbit] rabbit_quorum_queue = True rabbit_transient_quorum_queue = True rabbit_qos_prefetch_count = 1 use_queue_manager = True rabbit_stream_fanout = True or similar. Finally I recommend upgrade to the latest rabbitmq version since a lot of fixes for quorum queues were added in the last releases. Cheers, Arnaud. On 16.01.26 - 14:29, Francesco Di Nucci wrote:
Thanks,
until now I was using a single node, now the deployment has scaled and I'll go for a cluster, so quorum queues be it :)
-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples
Email: francesco.dinucci@na.infn.it
On 16/01/26 09:53, Thomas Goirand wrote:
On 1/15/26 10:44 AM, Francesco Di Nucci wrote:
Hi all,
I'm upgrading from OpenStack Caracal to Epoxy on EL, using RDO packages. I see that CentOS Stream Messaging SIG still packages RabbitMQ 3.8, that is EOL.
Should I still use it or switch to a more recent release, like 3.13 or pass to 4.x series? Has anyone tried it?
Thanks in advance
Hi,
Not sure about RDO and CentOS/Red Hat, but you have to know RabbitMQ 4.x doesn't have HA queues anymore. So if you are to upgrade, you must switch to quorum queues. Not sure as well if your system supports it.
Cheers,
Thomas Goirand (zigo)