I'm moving a thread we had with some vmware guys to this list to make it public.
We had a problem with quantum deadlocking when it got several requests in quick succession. Aaron suggested we set sql_dbpool_enable = True. We did and it seemed to resolve our issue. What are the downsides of turning on sql_dbpool_enable? Should it be on by default? Thanks, Jay >> We are currently experience the following problem in our environment: >> issuing 5 'quantum port-create' commands in parallel effectively deadlocks quantum: >> >> $ for n in $(seq 5); do echo 'quantum --insecure port-create stage-net1'; done | parallel >> An unknown exception occurred. >> Request Failed: internal server error while processing your request. >> An unexpected error occurred in the NVP Plugin:Unable to get logical switches On Jun 21, 2013, at 9:36 AM, Aaron Rosen <aro...@vmware.com> wrote: > We've encountered this issue as well. I'd try enabling: > # Enable the use of eventlet's db_pool for MySQL. The flags sql_min_pool_size, > # sql_max_pool_size and sql_idle_timeout are relevant only if this is enabled. > > sql_dbpool_enable = True > > in nvp.ini to see if that helps at all. In our internal cloud we removed the > creations of the lports in nvp from the transaction. Salvatore is working on > an async back-end to the plugin that will solve this and improve the plugin > performance.
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
