94f3ce0c78
By default ha-promote-on-shutdown=when-synced. However 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 This patch adds the option to change the ha-promote-on-shutdown definition, using the flag `rabbitmq_ha_promote_on_shutdown`. This value is unset by default to avoid any unexpected changes to the RabbitMQ definitions.json file, as that would trigger an unexpected restart of RabbitMQ during the next deploy. Related-Bug: #1954925 Change-Id: I2146bda2c72ddac2c9923c6941b0596395fd9ab5
14 lines
698 B
YAML
14 lines
698 B
YAML
---
|
|
features:
|
|
- |
|
|
The config option `rabbitmq_ha_promote_on_shutdown` has been added, which
|
|
allows changing the RabbitMQ definition `ha-promote-on-shutdown`. By
|
|
default `ha-promote-on-shutdown` is "when-synced". We recommend changing
|
|
this to be "always". This basically means we don't mind losing some
|
|
messages, instead we give priority to rabbitmq availability. This is most
|
|
relevant when restarting rabbitmq, such as when upgrading. Note that
|
|
setting the value of this flag, even to the default value of "when-synced",
|
|
will cause RabbitMQ to be restarted on the next deploy.
|
|
For more details please see:
|
|
https://www.rabbitmq.com/ha.html#cluster-shutdown
|