Skip to content

Commit 4bffd9f

Browse files
authored
Tweak some wording in delay transfer documentation (#8165)
1 parent 06e490b commit 4bffd9f

2 files changed

Lines changed: 10 additions & 3 deletions

File tree

transports/rabbitmq/delayed-delivery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,4 +185,4 @@ partial: disabledelayeddelivery
185185

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

188-
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.
188+
Upgrading RabbitMQ by using [blue-green deployments](https://www.rabbitmq.com/docs/upgrade#blue-green-deployment) is more complicated because delayed messages cannot be moved with standard tools like the [shovel](https://www.rabbitmq.com/docs/shovel) which are not aware of the how the delay infrastructure is implemented. The [`delays transfer`](operations-scripting.md#delays-transfer) command should be used to move delayed messages from one broker to another.

transports/rabbitmq/operations-scripting_content_rabbit_[11,).partial.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,13 @@ rabbitmq-transport delays migrate [options]
6161
`--disableCertValidation`: Disable remote certificate validation when connecting to the broker<br />
6262
`--routingTopology` | `-r` : The routing topology to use<br />
6363

64+
> [!NOTE]
65+
> 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:
66+
>
67+
> ```
68+
> rabbitmq-transport delays create --connectionString "amqp://user:pass@destination-host"
69+
> ```
70+
6471
### `delays transfer`
6572
6673
Use this command to transfer delayed messages from one broker to another:
@@ -93,7 +100,7 @@ rabbitmq-transport delays transfer [options]
93100
> 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:
94101
>
95102
> ```
96-
> rabbitmq-transport delays create --connectionString "amqp://user:pass@destination-host" --managementApiUrl "http://destination-host:15672"
103+
> rabbitmq-transport delays create --connectionString "amqp://user:pass@destination-host"
97104
> ```
98105
99106
> [!NOTE]
@@ -106,7 +113,7 @@ rabbitmq-transport delays transfer [options]
106113
#### Usage example
107114
108115
```
109-
rabbitmq-transport delays transfer --sourceConnectionString "amqp://user:pass@source-host" --destinationConnectionString "amqp://user:pass@destination-host"
116+
rabbitmq-transport delays transfer --sourceConnectionString "amqp://user:pass@source-host" --destinationConnectionString "amqp://user:pass@destination-host"
110117
```
111118
112119
### `delays verify`

0 commit comments

Comments
 (0)