Opened 8 years ago

Closed 6 years ago

#8414 closed (fixed)

multiple sites on one memcached

Reported by: urban Owned by: nobody
Component: Core (Cache system) Version: 1.2
Severity: Keywords: cache prefix session cached_db
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: yes Patch needs improvement: no
Easy pickings: UI/UX:


For every site which use for example CacheMiddleware we need to run new memcached instance, its not efficient with few small sites. I think that adding a key_prefix to the CACHE_BACKEND params will solve this problem. I've attached patch aganist memcache backend.

Attachments (1)

cahche.patch (1.8 KB) - added by urban 8 years ago.

Download all attachments as: .zip

Change History (7)

Changed 8 years ago by urban

Attachment: cahche.patch added

comment:1 Changed 8 years ago by Thomas Kerpe

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Resolution: invalid
Status: newclosed

What about just using CACHE_MIDDLEWARE_KEY_PREFIX?

I understand that will exactly solve the issue so I'm closing the ticket.
If that's not the issue feel free to reopen and comment.

comment:2 Changed 8 years ago by urban

Resolution: invalid
Status: closedreopened

It solves some problems, but not all, cache can be also set in other (than the CacheMiddleware) aplications, so maybe reimplement it in the cache framework instead of only in CacheMiddleware?

comment:3 Changed 8 years ago by Thomas Kerpe

Resolution: invalid
Status: reopenedclosed

With only this informations the issue is invalid since it describes no bug or new feature.
Describe it clearer maybe with a testcase.

comment:4 Changed 8 years ago by (none)

milestone: post-1.0

Milestone post-1.0 deleted

comment:5 Changed 6 years ago by mordicuac

Keywords: session cached_db added
Needs tests: set
Resolution: invalid
Status: closedreopened
Version: SVN1.2

Using cached_db backend for session sharing memcached with diferent django sites may create session_id conflicts in memcached, using CACHE_MIDDLEWARE_KEY_PREFIX in cache backend solve it.

comment:6 Changed 6 years ago by Russell Keith-Magee

Resolution: fixed
Status: reopenedclosed

A site-wide cache prefix was added in [14623]

Note: See TracTickets for help on using tickets.
Back to Top