nova-scheduler also loads deleted instances at startup
Bug #1524114 reported by
Belmiro Moreira
This bug report is a duplicate of:
Bug #1524421: Host Manager reads deleted instance info on startup.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Low
|
Tardis Xu |
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_
Adding the filter: {"deleted": False} fixes the problem.
Changed in nova: | |
status: | New → In Progress |
To post a comment you must log in.
Hi Belmiro Moreira,
I can reproduce your bug, and the nova-scheduler filters all the instances indeed.