-
Notifications
You must be signed in to change notification settings - Fork 4k
QQ: a delivery-limit of -1 disables the delivery limit. #12250
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
Conversation
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.
@ansd you are right, for this setting from now on we should simply pick the operator policy value and not the lower or higher one. So, we need to tweak the resolving function. |
unfortunately it isn't a simple as that as the policy resolution code doesn't include queue arg values. i'd have to add some code to a do a resolution based on all of queue arg, policy and operator policy. Alternatively we treat all values above some limit, say 65535, as |
Alt we could just say that any policy would override the queue arg if the queue arg is negative. |
@kjnilsson I like the idea with values above the |
Yes, I think the "more conservative" value should always win for Examples:
This allows operators to set guardrails via operator policies while applications can optionally choose a more conservative setting. In addition, this resolution strategy won't break applications upgrading from 3.13 to 4.0. |
For cases where users want to live a bit more dangerously this commit maps a delivery limit of -1 (or any negative value) such that it disables the delivery limit and restores the 3.13.x behaviour.
67b9939
to
e81feb5
Compare
I went with this approach in the end. -1 isn't without precedence as means of turning some facility off so in this sense it maybe less surprising. |
To mention that the default can be set to unlimited if the delivery-limit is set to -1.
QQ: a delivery-limit of -1 disables the delivery limit. (backport #12250)
For cases where users want to live a bit more dangerously this commit maps a delivery limit of -1 (or any negative value) such that it disables the delivery limit and restores the 3.13.x behaviour.