Comment 4 for bug 1579128
Revision history for this message
| Roman Podoliaka (rpodolyaka) wrote Re: Lost communication between nova-conductor and nova-compute | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
>>> Interesting that the status of nova-computes stays "up" even if it cannot receive the reply message. So it looks like after some point nova-conductor doesn't have resources (threads?) to process incoming messages and update DB.
it does not need to: by the time nova-conductor tries to send a reply it has already updated the corresponding row in the DB.
My understanding was that nova-conductor actually receives RPC calls, but it just can't send replies, as the reply queues are missing for some reason.