Comment 7 for bug 1420848
Revision history for this message
| Chris Friesen (cbf123) wrote Re: nova-compute service spuriously marked as "up" when disabled | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I don't think it's acceptable, no. Any operation involving the scheduler could end up trying to place an instance on the "down" compute node for that minute.
And if we were enabling the service rather than disabling it (or doing any other operation on the service) then we could end up in a state where the scheduler thinks it's available. That could result in operations taking a long time as they block waiting for the RPC timeout since of course the compute node would never respond.
I think it's clearly a flawed design to rely on automatic database row timestamps for status, when both system and user-triggered operations cause those timestamps to be updated.