Skip to content

Improvements for delayed delivery tranfer cli tool for RabbitMQ #8163

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.

Sign up for GitHub

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
irinascurtu merged 6 commits into from
Apr 9, 2026
+21 −1
Merged

Improvements for delayed delivery tranfer cli tool for RabbitMQ #8163

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
52254af
Samples for delayed delivery
irinascurtu Apr 8, 2026
ffa478d
Removed the sample
irinascurtu Apr 8, 2026
e309a30
Update transports/rabbitmq/operations-scripting_content_rabbit_[11,).…
irinascurtu Apr 9, 2026
2626ff3
Update delayed-delivery.md
irinascurtu Apr 9, 2026
6b0004b
added reference to delays transfer
irinascurtu Apr 9, 2026
9b85e59
fix path
irinascurtu Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion transports/rabbitmq/delayed-delivery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,4 +185,4 @@ partial: disabledelayeddelivery

When upgrading the RabbitMQ cluster, it is recommended to use the [rolling (in-place)](https://www.rabbitmq.com/docs/upgrade#rolling-upgrade) method.

Due to the way the native delayed delivery infrastructure is implemented, upgrading RabbitMQ by using [blue-green deployments](https://www.rabbitmq.com/docs/upgrade#blue-green-deployment) is more complicated and requires the specialized shovelling of delayed messages in order to avoid message loss. Contact [Particular support](https://customers.particular.net/request-support) for further details on this scenario.
Due to the way the native delayed delivery infrastructure is implemented, upgrading RabbitMQ by using [blue-green deployments](https://www.rabbitmq.com/docs/upgrade#blue-green-deployment) is more complicated and requires the specialized shovelling of delayed messages in order to avoid message loss. You can use one of the supported cli tools like [`delays transfer`](operations-scripting.md#delays-transfer) to aid with the shoveling.
20 changes: 20 additions & 0 deletions transports/rabbitmq/operations-scripting_content_rabbit_[11,).partial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,26 @@ rabbitmq-transport delays transfer [options]
`--disableCertValidation` : Disable remote certificate validation when connecting to the broker<br />
`--routingTopology` | `-r` : The routing topology to use<br />

> [!NOTE]
> Before running this command, the destination broker must have the v2 delay infrastructure in place. Use the [`delays create`](#delays-create) command to set it up:
>
> ```
> rabbitmq-transport delays create --connectionString "amqp://user:pass@destination-host" --managementApiUrl "http://destination-host:15672"
> ```

> [!NOTE]
> All exchanges and queues that exist on the source broker must also exist on the destination broker before running this command. Use the [`endpoint create`](#endpoint-create) command for each endpoint:
>
> ```
> rabbitmq-transport endpoint create <endpointName> --connectionString "amqp://user:pass@destination-host"
> ```

#### Usage example

```
rabbitmq-transport delays transfer --sourceConnectionString "amqp://user:pass@source-host" --destinationConnectionString "amqp://user:pass@destination-host"
```

### `delays verify`

Use this command to verify broker requirements for using the v2 delay infrastructure:
Expand Down