RabbitMQ timeout causes crashes.
Issue
- RabbitMQ's default 5 second timeout doesn't match the 30 second timeout set for the resource in pacemaker.
- In systems with high resource use this can create a situation where RabbitMQ fences itself but from the standpoint of Pacemaker the resource is up and running and there are no actions to correct the issue.
Environment
Red Hat Openstack Platform 7
Red Hat Openstack Platform 8
Red Hat Openstack Platform 9
Red Hat Openstack Platform 10
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.