registry team mailing list archive

[Eric Day <649806@xxxxxxxxxxxxxxxxxx>]

Yeah, a couple have these have already been fixed. I changed the
consumer code to actually wait rather than busy poll every 100ms, which
means each consumer needs to have it's own connection. Since these are
short lived we can keep a pool of cached connections to reuse so we
don't have the connection setup cost on every use. We can add a pool
anywhere we are currently using singleton connections.

-- 
AMQP concurrencty problem in API server
https://bugs.launchpad.net/bugs/649806
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.