8e3c523fd7
When rabbit is failing for a specific quorum queue, the only thing to do is to delete the queue (as per rabbit doc, see [1]). So, to avoid the RPC service to be broken until an operator eventually do a manual fix on it, catch any INTERNAL ERROR (code 541) and trigger the deletion of the failed queues under those conditions. So on next queue declare (triggered from various retries), the queue will be created again and the service will recover by itself. Closes-Bug: #2028384 Related-bug: #2031497 [1] https://www.rabbitmq.com/quorum-queues.html#availability Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com> Change-Id: Ib8dba833542973091a4e0bf23bb593aca89c5905
10 lines
347 B
YAML
10 lines
347 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Auto-delete the failed quorum rabbit queues.
|
|
When rabbit is failing for a specific quorum queue, delete the queue
|
|
before trying to recreate it.
|
|
This may happen if the queue is not recoverable on rabbit side.
|
|
See https://www.rabbitmq.com/quorum-queues.html#availability for more
|
|
info on this specific case.
|