-
Notifications
You must be signed in to change notification settings - Fork 32
⬆️ upgrading rabbitmq to 4.1.2 ⚠️🚨 #8109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⬆️ upgrading rabbitmq to 4.1.2 ⚠️🚨 #8109
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #8109 +/- ##
==========================================
- Coverage 88.21% 88.19% -0.02%
==========================================
Files 1883 1883
Lines 72416 72419 +3
Branches 1272 1273 +1
==========================================
- Hits 63883 63873 -10
- Misses 8159 8170 +11
- Partials 374 376 +2
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
YuryHrytsuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks,
What are the effects of making these queues durable?
pcrespov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx
|
sanderegg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks
It makes them persist to disk.
|
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at f976a56 |



When this is released to a deployment:
deferred_managerand remove them (should be 2)deferred_manageranddynamic-schedulerand remove them (should be 5 or more)dynamic-schedulerservice.What do these changes do?
✅ Upgrading rabbitmq to
4.1.2is free of risks with regard to thex-deathheader. The code always used it in the intended case.✅ Removed the warning relative to
transient_nonexcl_queuesby making the queues durable, which has no negative impact:✅ If
declare_queuewould create atransient_nonexcl_queueswarning in RabbitMQ, it will now raise an error.transient_nonexcl_queueson the following:I found the following issue in the community: celery/kombu#2237
Related issue/s
3.13and4.1rabbitmq versions #8077How to test
Dev-ops