nova config to override sqlalchemy defaults

Bug #1084177 reported by JB
12
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.

Revision history for this message
Chuck Short (zulcss) wrote :

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.

Changed in nova:
status: New → Invalid
Revision history for this message
Vish Ishaya (vishvananda) wrote :

The sql_max_pool_size was only recently added into to grizzly, so perhaps fix committed is better for this.

Changed in nova:
status: Invalid → Fix Committed
importance: Undecided → Low
assignee: nobody → Chris Behrens (cbehrens)
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-1
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-1 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.