Comment 6 for bug 1360446
Revision history for this message
| Morgan Fainberg (mdrnstm) wrote Re: Keystone server didn't reuse connections to memcached | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@zzzeek Just missed you on IRC, but I am not sure about the threadlocal issue (doesn't ring a bell). This appears to just be lack of re-use of the actual client connection object to memcached. We got around some of this issue in keystoneclient by using a memcachepool implementation that creates up to the number of worker threads worth of memcache connections and when it's done with the connection it puts it back into the pool (with a little logic to handle dead connections).
In this case i'm guessing they have a lot of activity and some connections aren't being closed due to either GC delay or other memcached client library oddities, so under load you end up with stale connections which cause this related error case.