a87810db7e
Changes the default value of `rabbitmq-ha-promote-on-shutdown` to `"always"`. We are seeing issues with RabbitMQ automatically recovering when nodes are restarted. https://www.rabbitmq.com/ha.html#cluster-shutdown Rather than waiting for operator interventions, it is better we allow recovery to happen, even if that means we may loose some messages. A few failed and timed out operations is better than a totaly broken cloud. This is achieved using ha-promote-on-shutdown=always. Note, when a node failure is detected, this is already the default behaviour from 3.7.5 onwards: https://www.rabbitmq.com/ha.html#promoting-unsynchronised-mirrors Related-Bug: #1954925 Change-Id: I484a81163f703fa27112df22473d657e2a9ab964
12 lines
558 B
YAML
Executable File
12 lines
558 B
YAML
Executable File
---
|
|
upgrade:
|
|
- |
|
|
The RabbitMQ variable `rabbitmq-ha-promote-on-shutdown` now defaults to
|
|
`"always"`. This only has an effect if
|
|
`om_enable_rabbitmq_high_availability` is set to `True`. When
|
|
`ha-promote-on-shutdown` is set to `always`, queue mirrors are promted on
|
|
shutdown even if they aren't fully synced. This means that value
|
|
availability over the risk of losing some messages. Note that the contents
|
|
of the RabbitMQ definitions.json are now changed, meaning RabbitMQ
|
|
containers will be restarted on next deploy/upgrade.
|