Public bug reported:
nova-scheduler is loading all instances (including deleted) at startup.
Experienced problems when each node has >6000 deleted instances, even when
using batches of 10 nodes.
Each query can take several minutes and transfer several GB of data.
This prevented nova-scheduler connect to rabbitmq.
###
When nova-scheduler starts it calls "_async_init_instance_info()" and it does
an "InstanceList.get_by_filters" that uses batches of 10 nodes. This uses
"instance_get_all_by_filters_sort", however "Deleted instances will be returned
by default, unless there's a filter that says otherwise".
Adding the filter: {"deleted": False} fixes the problem.
** Affects: nova
Importance: Undecided
Status: New
** Tags: scheduler
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1524114
Title:
nova-scheduler also loads deleted instances at startup
Status in OpenStack Compute (nova):
New
Bug description:
nova-scheduler is loading all instances (including deleted) at
startup.
Experienced problems when each node has >6000 deleted instances, even when
using batches of 10 nodes.
Each query can take several minutes and transfer several GB of data.
This prevented nova-scheduler connect to rabbitmq.
###
When nova-scheduler starts it calls "_async_init_instance_info()" and it does
an "InstanceList.get_by_filters" that uses batches of 10 nodes. This uses
"instance_get_all_by_filters_sort", however "Deleted instances will be returned
by default, unless there's a filter that says otherwise".
Adding the filter: {"deleted": False} fixes the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524114/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
