Dynamic shovel publisher not blocked on low disk alarm

[Olivier Monnier]

Hi,

I'm facing an unexpected behavior, as far as I understand the docs.

My version:

- RabbitMQ 3.9.13

- Erlang 24.2.1

I'm using dynamic shovels configured like this:

{

    "ack-mode": "on-confirm",

    "dest-add-forward-headers": true,

    "dest-add-timestamp-header": true,

    "dest-exchange": "outputexchange",

    "dest-exchange-key": "fromshovel",

    "dest-protocol": "amqp091",

    "dest-uri": "amqp://",

    "src-delete-after": "never",

    "src-protocol": "amqp091",

    "src-queue": "inputqueue",

    "src-uri": "amqp://172.17.0.1:5673/%2F"

}

When RabbitMQ low disk alarms fires, publishers are expected to be blocked as we can see in the logs:

2023-01-31 13:54:18.494092+00:00 [info] <0.297.0> Free disk space is insufficient. Free bytes: 566611968. Limit: 629145600

2023-01-31 13:54:18.494174+00:00 [warn] <0.293.0> *** Publishers will be blocked until this alarm clears ***

But the shovel continues to publish on the destination exchange. Only other kind of publishers connections are in "blocked" state. The shovel connection is still in "Idle" state.

Could anyone please share some feedback ?

Thanks