We knows that nova-compute will do report_state to update the service information in DB, And the default report_interval is 5s.
When scheduler run a new instance, it will check the time that nova-compute updated. If the interval is longer than 60 seconds, Scheduler see the host is dead.
But when the host(nova-compute) running a lot of instances ( about 70+) . The report_interval sometimes can be greater then 2minutes. This will result in ERROR in scheduler.
I think report_state should be in a thread, rather than in a eventlet.spawn.
What about guys think?
We knows that nova-compute will do report_state to update the service information in DB, And the default report_interval is 5s.
When scheduler run a new instance, it will check the time that nova-compute updated. If the interval is longer than 60 seconds, Scheduler see the host is dead.
But when the host(nova-compute) running a lot of instances ( about 70+) . The report_interval sometimes can be greater then 2minutes. This will result in ERROR in scheduler.
I think report_state should be in a thread, rather than in a eventlet.spawn.
What about guys think?
Thanks