[octavia] usage of SELECT .. FOR UPDATE

Mohammed Naser mnaser at vexxhost.com
Sun Aug 30 15:41:26 UTC 2020

Hi everyone,

We're being particularly hit hard across different deployments where
Octavia has several SELECT .. FOR UPDATE queries which are causing
load balancers to fail to provision properly.

- spare_pools: This usually hits on rolling restarts of o-housekeeping
as they all seem to try to capture a lock --

- quota: This hits when provisioning a lot of load balancers in
parallel.  For example in cases when using Heat --

These hurt quite a lot in a busy deployment and result in a poor user
experience unfortunately.  We're trying to off-load Octavia to it's
own database server but that is more of a "throw power at the problem"
solution.  I can imagine that we can probably likely look into a
better/cleaner alternative that avoids this entirely?

I'm happy to try and push for some of this work on our side.


Mohammed Naser

More information about the openstack-discuss mailing list