Comment 2 for bug 1320617
Revision history for this message
| Matt Riedemann (mriedem) wrote Re: failed to reach ACTIVE status within the required time (196 s). Current status: SAVING | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
For example, when this failed in the log link above, around time 21:44:09.859, you can see in dstat that ceilometer agent notification was really impacting the CPU:
http://
09-05 21:44:09| 68 14 16 1 0 1|3933M 184M 2529M 837M| 0 0 | 48k 7780k|5.00 192 |4588 8707 |8.20 6.81 3.49| 13 0 52|ceilometer-
It'd be cool if we could dynamically adjust timeouts based on current system load...but maybe that's just overly complicating things - the alternative is probably just making ceilometer better and consuming less CPU all the time.