[Suggestion] Correct blog post around behavior of 3.13 and CQv2 #12330
-
RabbitMQ series3.13.x Operating system (distribution) usedlinux How is RabbitMQ deployed?Community Docker image What would you like to suggest for a future version of RabbitMQ?
We can't find any documentation that corroborates this and it caused a bit of confusion. After testing on a newly upgrades 3.13 cluster from just using the admin UI to make a new queue, it reports that it is CQv1 by default. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes, we were planning on making it the default in 3.13 but ultimately decided against it. I thought we updated the post, but maybe not. Anyway, I will fix this, thanks. CQv2 becomes the only option in RabbitMQ 4.0. Any CQv1 will be automatically migrated if you upgrade to 4.0. I'd recommend switching to CQv2 on 3.13 (you will get the benefits of v2 and a simpler upgrade to 4.0) |
Beta Was this translation helpful? Give feedback.
Yes, we were planning on making it the default in 3.13 but ultimately decided against it. I thought we updated the post, but maybe not. Anyway, I will fix this, thanks.
CQv2 becomes the only option in RabbitMQ 4.0. Any CQv1 will be automatically migrated if you upgrade to 4.0. I'd recommend switching to CQv2 on 3.13 (you will get the benefits of v2 and a simpler upgrade to 4.0)