cmemcache and python-memcache hashing differences
|Reported by:||Ludvig Ericson||Owned by:||nobody|
|Component:||Core (Cache system)||Version:||master|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
There needs to be support for decidedly using either only python-memcached or cmemcache.
The reason being that the two libraries hash different ways - if you have a box with cmemcache and two without, one of those boxes will store sessions on a different memcached than the other two.
I'm not sure what to do about it, but Malcolm wants documentation and/or a setting with which you can tell Django "use only this library" and fail if it isn't found.
Arguably, this should be something that the two libraries come together on, but at least solving it on our part would be nice.
It might be relevant that I've made a hackesque module which monkey patches python-memcached to hash the same way as cmemcache, see http://pypi.python.org/pypi/cmemcache_hash
Change History (9)
comment:1 Changed 8 years ago by
|Summary:||cmemcache and python-memcache → cmemcache and python-memcache hashing differences|