diff options
| author | John Garbutt <john.garbutt@stackhpc.com> | 2021-12-17 16:20:32 +0000 |
|---|---|---|
| committer | Matt Crees <mattc@stackhpc.com> | 2023-02-09 13:49:07 +0000 |
| commit | 94f3ce0c78998e29fcc034a9b0844f9d6d602807 (patch) | |
| tree | aaa06b67e69f5df8e00dacc0419ea793fac9690b /tools | |
| parent | ef49c7440f3f2de7c13bc0ac9f8e961adef5de9a (diff) | |
| download | kolla-ansible-94f3ce0c78998e29fcc034a9b0844f9d6d602807.tar.gz kolla-ansible-94f3ce0c78998e29fcc034a9b0844f9d6d602807.zip | |
RabbitMQ: Support setting ha-promote-on-shutdown
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
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions