#15729: Cache middleware issues after restart when using mod_wsgi with PyLibMC
--------------------------------------+-----------------------------------
Reporter: jsdalton | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Core (Cache system)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
--------------------------------------+-----------------------------------
Comment (by jsdalton):
Replying to [comment:3 toxik]:
> It's actually not even a fault pylibmc can handle - the underlying
libmemcached library should be handling this. There are patches floating
around the internet regarding libmemcached's handling of failures but I
would suggest pushing for this issue on the libmemcached mailing list.
Yeah, I don't know. I guess I just feel like if you're deploying on a
stack that's "recommended" by the official Django documentation and a
failry typical action within that stack (restarting memcached service)
causes an application error within Django that literally brings your
application to a halt, then that's perhaps something that should at least
be mentioned in the documentation? I mean, I saw the addition of PyLibMC
and had heard good things about it, and went through the trouble of
configuring and deploying it, and only very fortunately caught the issue
while it was still staging so that it did not make it production. It seems
like a huge red flag to using the library.
But I completely understand your line of reasoning. It's not something it
would appear Django can do anything about directly, but by the same token
should that library be supported?
--
Ticket URL: <http://code.djangoproject.com/ticket/15729#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
