This behavior is the way the python memcache clients themselves work. This isn't specific to dogpile, keystone, or anything else.
The basic behavior is 'try and wait for a timeout'. Not sure what the best solution to this will be in the short-term. In the long term, the real solution will be non-persistent (no need to store) the tokens, which would eliminate the need for memcache in this regard.
This behavior is the way the python memcache clients themselves work. This isn't specific to dogpile, keystone, or anything else.
The basic behavior is 'try and wait for a timeout'. Not sure what the best solution to this will be in the short-term. In the long term, the real solution will be non-persistent (no need to store) the tokens, which would eliminate the need for memcache in this regard.