Skip to content

Commit 4d2a9dd

Browse files
committed
QQ: delivery-limit cannot be set to -1 through a policy
1 parent 5d35132 commit 4d2a9dd

File tree

2 files changed

+10
-6
lines changed

2 files changed

+10
-6
lines changed

docs/quorum-queues/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -366,9 +366,8 @@ dropped messages are retained for some time after.
366366

367367
Starting with RabbitMQ 4.0, the delivery limit for quorum queues defaults to 20.
368368

369-
The 3.13.x era behavior where there was no limit can be restored by setting the limit to `-1`
370-
using an [optional queue argument](./queues#optional-arguments) at declaration time or using a policy as demonstrated below.
371-
369+
The 3.13.x era behavior where there was no limit can be restored by setting `x-delivery-limit=-1`
370+
[optional queue argument](./queues#optional-arguments) when declaring a queue.
372371

373372
:::
374373

@@ -378,6 +377,9 @@ See [repeated requeues](#repeated-requeues) for more details.
378377

379378
It is possible to set a delivery limit for a queue using a [policy](./policies) argument, `delivery-limit`.
380379

380+
The value of `-1`, which disables the limit altogether, cannot be currently set through a policy - this
381+
can only be done with `x-delivery-limit=-1` queue argument during queue declaration.
382+
381383
#### Overriding the Limit
382384

383385
The following example sets the limit to 50 for queues whose names begin with

versioned_docs/version-4.1/quorum-queues/index.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -366,9 +366,8 @@ dropped messages are retained for some time after.
366366

367367
Starting with RabbitMQ 4.0, the delivery limit for quorum queues defaults to 20.
368368

369-
The 3.13.x era behavior where there was no limit can be restored by setting the limit to `-1`
370-
using an [optional queue argument](./queues#optional-arguments) at declaration time or using a policy as demonstrated below.
371-
369+
The 3.13.x era behavior where there was no limit can be restored by setting `x-delivery-limit=-1`
370+
[optional queue argument](./queues#optional-arguments) when declaring a queue.
372371

373372
:::
374373

@@ -378,6 +377,9 @@ See [repeated requeues](#repeated-requeues) for more details.
378377

379378
It is possible to set a delivery limit for a queue using a [policy](./policies) argument, `delivery-limit`.
380379

380+
The value of `-1`, which disables the limit altogether, cannot be currently set through a policy - this
381+
can only be done with `x-delivery-limit=-1` queue argument during queue declaration.
382+
381383
#### Overriding the Limit
382384

383385
The following example sets the limit to 50 for queues whose names begin with

0 commit comments

Comments
 (0)