RabbitMQ 4.x default queue type

[Kris Reese]

We have an application that serves as a common library other applications utilize for its function to create worker or listener queues.  Declaration of queues via this common library does not set any of the optional arguments such as x-queue-type, and therefore, the default is classic.  Upon the release of RabbitMQ 4.x, will the default change to quorum? Assuming we do not care about message loss, we’re considering building RabbitMQ 4.x (once available) alongside our existing 3.11.x, and pointing our applications to the upgraded side, and let them recreate their exchanges/queues and go about their business as our migration strategy.  Does this sound like a reasonable approach?

Otherwise, is there any information that can be shared on how an upgrade from 3.x to 4.x will handle the existence of classic queues?

Thank you!

Kris

[Michal Kuratczyk]

Hi,

We don't plan on changing the default queue type. Classic queues still have many valid use-cases and with classic queues v2 (already available in 3.10 and 3.11 as opt-in, but much better in 3.12 and the default/only version in the future) they will offer plenty of performance, and low memory usage. In your case, an in-place upgrade should suffice, but of course you can install 4.0 alongside or perform blue-green.

If you have a test env, where you could try `main` or 3.12 release candidate with CQv2 and report back that'd be highly appreciated.

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/a6c90ef0-7d9d-4773-bbc2-930803aaa319n%40googlegroups.com.

--

Michał

RabbitMQ team

[Kris Reese]

Thank you for the insight.  This helps a lot!  We're currently running 3.11.x and if we go to 3.12, will be happy to share our experience with CQv2.  Quick question on that though?  In 3.12, can CQv2 be mirrored?

[Michal Kuratczyk]

Hi,

It's a rarely used combination and since we plan to remove mirroring, we don't pay too much attention to it, but yes CQv2 can be mirrored until 4.0.

Thanks to CQv2 improvements mirrored CQv2 offers higher throughput/lower latency in many scenarios, but there are also cases where it's worse.

However, I'd highly recommend going straight to quorum queues for use cases that require replication.

Best,

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/c593abd3-f48c-4ed0-ad56-b213c87e715en%40googlegroups.com.

--

Michał

RabbitMQ team

[Kris Reese]

Thank you!