Thanks, luckily I can have a downtime, so I can skip some intermediate releases even if it halts operations -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci@na.infn.it On 15/01/26 11:41, Eugen Block wrote:

Hi,

we upgraded to Epoxy last year as well. Since our cloud runs on (Ubuntu) packages (not containerized), we were kind of forced to upgrade RabbitMQ as well (if we didn't want to fiddle with locking packages etc.). The transition wasn't very smooth in that regard though, we had to use RabbitMQ containers to gradually upgrade from 3.9 to 3.10 and 3.11. The RabbitMQ package version for Ubuntu 24 was 3.12, and we couldn't just skip because of missing features which had to be enabled in 3.10/3.11. So there was a short downtime for the services because we couldn't make it work with mixed versions. So we shut down RabbitMQ, started a 3.10 container mapping the rabbit database, stopped it, started a 3.11 container, stopped it. Then started the rabbit systemd service again. I hope we don't have to do it this way too often. :-D Maybe at some point we will decide to migrate to kolla-ansible, I don't know. For now we'll stay on packages as long as possible.

Regards, Eugen

Zitat von Francesco Di Nucci <francesco.dinucci@na.infn.it>:

...

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

-- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples

Email: francesco.dinucci@na.infn.it

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)

On 1/17/26 1:01 PM, Arnaud Morin wrote:

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. Hi Arnaud,

Why are you setting rabbit_qos_prefetch_count to just "1" ? Doesn't this prevent optimization by oslo.messaging? Cheers, Thomas Goirand (zigo)