Cached DB Session Backend
|Reported by:||jhenry||Owned by:||Jacob|
|Cc:||pytechd@…, jdunck@…, waylan@…, gabor@…, Peter Kese||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Right now, I consider the "cache" session backend to be broken, especially when used with the memcached session backend.
In a large memcached environment, servers enter and leave the memcached pool frequently. Each time this happens, the pool mapping changes and automatically logs users out (and loses their session data).
Attached is a new backend which is basically a copy of the DB session backend with a django.core.cache wrapper on accesses to the session data; all writes are write through to the database and cache and all reads come from memcache except in case of a memcache failure when it reads from the database.
Change History (25)
comment:6 Changed 9 years ago by
|Owner:||changed from Jeremy Dunck to Jacob|
|Status:||assigned → new|