>>> 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.
>>> 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.