#28342: Make PyLibMCCache backend catch exceptions when memcached server is down
-------------------------------------+-------------------------------------
Reporter: Julian Andrews | Owner: Joel
Type: | Andrews
Cleanup/optimization | Status: closed
Component: Core (Cache system) | Version: 3.0
Severity: Normal | Resolution: needsinfo
Keywords: memcached cache | Triage Stage: Accepted
pylibmc |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: assigned => closed
* resolution: => needsinfo
Comment:
I'm not sure about catching all kind of exceptions or even
`pylibmc.ConnectionError` or `pylibmc.ServerDown`. Consistency between
different backends for the same serves is not a strong argument for me.
`pylibmc` policy is strongly expressed in the
[http://sendapatch.se/projects/pylibmc/misc.html#exceptions docs]. Folks
using different libraries can expect different behaviors, and you can
always change your stack.
I think we should go back to the DevelopersMailingList and reach a strong
consensus to move it forward.
--
Ticket URL: <https://code.djangoproject.com/ticket/28342#comment:8>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.740c94a8534e7f71a21cb02e722d6043%40djangoproject.com.
