migration 153 takes extremely long amount of time
Bug #1155371 reported by
Brian Lamar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Brian Lamar | ||
Bug Description
Currently migration 153 inserts 10 rows per instance in the database. For new/small installations this is relatively quick, but for large installations this can take some time.
For example, if an installation has 100,000 deleted instances, this migration will attempt to insert 1,000,000 new rows.
| Changed in nova: | |
| status: | New → In Progress |
| assignee: | nobody → Brian Lamar (blamar) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → grizzly-rc1 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 767aa58c29546b5
Author: Brian Lamar <email address hidden>
Date: Thu Mar 14 13:56:40 2013 -0400
Update migration 153 for efficiency.
Currently migration 153 inserts 10 rows per instance in the database.
For new/small installations this is relatively quick, but for large
installations this can take some time.
This change modifies the migration to only insert records for
non-deleted instances and makes bulk inserts (10 rows are inserted
with each query, instead of 1 per query) for added speed.
Fixes bug 1155371
Change-Id: I88a6cec2c11736