Fuel for OpenStack

  1. Bug #1463433
  2. Comment #10

Comment 10 for bug 1463433

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Re: rabbitmq was down on one of controllers during shaker test but there are multiple "Timed out waiting for reply to ID" events logged by Oslo.messaging after rabbitmq recovered from partitioning

https://www.rabbitmq.com/alarms.html - shows just one node hitting the limit with block everything

When running RabbitMQ in a cluster, the memory and disk alarms are cluster-wide; if one node goes over the limit then all nodes will block connections.