618250adbc
Changes in oslo.messaging for 2023.1 exposed a known race
condition in RabbitMQ when dealing with non-HA classic queues.
When a RMQ cluster member is taken down, clients failing over
to other members may erroneously be told a queue exists when it
is in the process of being deleted. This can cause them to
permanently sit waiting for messages from a queue that no longer
exists until their services are restarted.
Making the reply queues HA resolves this issue, at the expense
of a x3 increase in reply queues across the cluster. My
assumption is that reply queues were previously excluded from HA
policy as a performance gain given their link to the number of
compute nodes in an OpenStack deployment.
Context: https://bugs.launchpad.net/oslo.messaging/+bug/2031512
Change-Id: Ia0a26fdfdfa09088c921f1530d4ac020b2bec290
(cherry picked from commit
|
||
|---|---|---|
| defaults | ||
| doc | ||
| examples | ||
| files | ||
| meta | ||
| releasenotes | ||
| tasks | ||
| templates | ||
| tests | ||
| vars | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| README.rst | ||
| Vagrantfile | ||
| bindep.txt | ||
| manual-test.rc | ||
| run_tests.sh | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack-Ansible RabbitMQ server
Ansible role to install OpenStack RabbitMQ server.
- Documentation for the project can be found at:
-
https://docs.openstack.org/openstack-ansible-rabbitmq_server/latest/
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-rabbitmq_server/
- The project source code repository is located at:
-
https://opendev.org/openstack/openstack-ansible-rabbitmq_server/
- The project home is at:
- The project bug tracker is located at: