nova config to override sqlalchemy defaults
Bug #1084177 reported by
JB
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Chris Behrens |
Bug Description
Bulk launch and bulk delete of VMs sometimes fails (for some VMs) with the following error in sqlalchemy
nova.rpc.amqp TimeoutError: QueuePool limit of size 5 overflow 10 reached, connection timed out, timeout 30
nova.conf does not seem to have flags to override the above sqlalchemy engine defalut values.
Changed in nova: | |
milestone: | none → grizzly-1 |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Actually there is a setting called "'sql_max_ pool_size" which is set to 5 which explains the problem you are getting if you bump it up then this problem wont occur.