Skip to content

QQ: introduce a default delivery limit (backport #11937) #12031

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

Merged
merged 3 commits into from
Aug 16, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 16, 2024

If the delivery_limit of a quorum queue is not set by queue arg and/or policy it will now be defaulted to 20.

Deliver limits are recommended for safe and smooth quorum queue operations. The downside is that poorly written applications and RabbitMQ configurations that frequently return messages to the queue now could be dropped when they reach the delivery limit. This is a breaking change in terms of some applications.

Hence, it will be recommended to put a blanket, low priority policy in place to set a dead letter configuration for all quorum queues to dead letter dropped messages to, e.g. a single stream, at least until applications and configurations can be properly updated.

This PR also exposes the delivery limit on the queue page (and adds a publisher count because it was easy).

Screenshot 2024-08-16 at 09 00 02
This is an automatic backport of pull request #11937 done by [Mergify](https://mergify.com).

If the delivery_limit of a quorum queue is not set by queue arg and/or
policy it will now be defaulted to 20.

(cherry picked from commit daecdb0)
To make it more visible that a default is in place.

Also added publisher count as it was easy to do so.

(cherry picked from commit 3a386f4)
@kjnilsson kjnilsson merged commit e97daad into v4.0.x Aug 16, 2024
199 checks passed
@kjnilsson kjnilsson deleted the mergify/bp/v4.0.x/pr-11937 branch August 16, 2024 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant