
When the RabbitMQ experience a rolling restart of its peers, the master of an HA queue fails over from one replica to another. If there are messages sent to the HA queue while some rabbit nodes are restarting, the latter will reconnect as unsynchronized slaves. It can happen that during a rolling restart, all rabbit nodes reconnect as unsynchronized, which prevents RabbitMQ to automatically elect a new Master for failover. This has other side effects on fanout queues and may prevent OpenStack notification to be consumed properly. Change the HA policy to always allow a promotion even when all replicas are unsynchronized. When such rare condition happens, rely on OpenStack client to retry RPC if they need to. Closes-Bug: #1823305 Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com> Change-Id: Id9bdd36aa0ee81424212e3a89185311817a15aee
Team and repository tags
puppet-tripleo
Lightweight composition layer for Puppet TripleO.
Contributing
- Free software: Apache License (2.0)
- Source: http://git.openstack.org/cgit/openstack/puppet-tripleo
- Bugs: http://bugs.launchpad.net/tripleo (tag: puppet)
- Documentation:
- TripleO: https://docs.openstack.org/tripleo-docs/latest/
- Testing with puppet: https://docs.openstack.org/puppet-openstack-guide/latest/contributor/testing.html
- Release Notes https://docs.openstack.org/releasenotes/puppet-tripleo
Description