dcs at tabblo.com
Wed Feb 14 13:10:11 UTC 2007
I'm having the same problem with key collisions with the python
binding, and I was wondering if you've made any progress. I haven't
been able to reproduce the problem in a test, but in production,
we'll encounter the problem all of a sudden after a while (the only
"solution" so far is to restart memcached). The server returns the
wrong value for the requested key. Not only that, but if you try a
get_many for key 'foo', you may get a response that has key 'bar' and
Since I haven't been able to reproduce this behavior in a test, I
don't yet know if it's the python binding or memcached itself.
Does anyone have any ideas?
> I am consistently getting key collisions. There are total of around
> 2000 key
> value pairs cached.
> This is how I prepare the key for memcached: md5.new(key).hexdigest
> () where
> key is the unique
> id for the database row that I want to cache.
> When I do a 'get' for a specific key, I get a value of a different
> I am using python-memcached as the client.
> This is causing lot of problems. If anyone has faced similar issues
> or has
> any suggestions do reply.
More information about the memcached