Loss of RabbitMQ requires restart of nova-compute
Bug #797338 reported by
Graham Hemingway
This bug report is a duplicate of:
Bug #794627: Handle RabbitMQ crash and attempt to reestablish connections and queues.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Today the server running RabbitMQ froze and had to be restarted. After the restart none of the communication between the AMPQ service and my nova-compute nodes worked. It appears that if the messaging service dies at any point, the only way to reestablish a connection with the nova-compute services is to restart nova-compute on all nodes.
Could we change this so that there is some periodic check by the nova-compute service to make sure it is still in touch with the Rabbit?
Thanks,
Graham
Revision history for this message
| Graham Hemingway (graham-hemingway) wrote | #1 |
To post a comment you must log in.
This is a duplicate of 794627. Sorry for the distraction.