sqlalchemy impl calls back to DB API
Bug #1154811 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Chris Behrens |
Bug Description
In 3 places, sqlalchemy has calls back to the DB API:
db.instance_
db.aggregate_
db.ec2_
While this an eventlet bug, when tpool is enabled.. The call path ends up being:
tpool.execute { sqlalchemy_method { tpool.execute{ sqlalchemy_method } } }
eventlet tries to deal with recursive tpool.execute()s but it seems to cause lockups.
Either way, it's not necessary to call back to DB API from the sqlalchemy backend, and I think that should be avoided.
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.
Fix proposed to branch: master /review. openstack. org/24372
Review: https:/