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.
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.
Reviewed: https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/822135 /opendev. org/openstack/ kolla-ansible/ commit/ 94f3ce0c78998e2 9fcc034a9b0844f 9d6d602807
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 94f3ce0c78998e2 9fcc034a9b0844f 9d6d602807
Author: John Garbutt <email address hidden>
Date: Fri Dec 17 16:20:32 2021 +0000
RabbitMQ: Support setting ha-promote- on-shutdown
By default ha-promote- on-shutdown= when-synced. However we are seeing /www.rabbitmq. com/ha. html#cluster- shutdown
issues with RabbitMQ automatically recovering when nodes are restarted.
https:/
Rather than waiting for operator interventions, it is better we allow on-shutdown= always.
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-
Note, when a node failure is detected, this is already the default /www.rabbitmq. com/ha. html#promoting- unsynchronised- mirrors
behaviour from 3.7.5 onwards:
https:/
This patch adds the option to change the ha-promote- on-shutdown ha_promote_ on_shutdown` . This
definition, using the flag `rabbitmq_
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: I2146bda2c72dda c2c9923c6941b05 96395fd9ab5