#25824: Assertions in libmemcached when multiple
django.core.cache.backends.memcached.PyLibMCCache backends used
-------------------------------+--------------------------------------
Reporter: mlowicki | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by charettes):
Alright, keep us updated.
FWIW Django stores aliased cache instances in a `threading.local`
[https://github.com/django/django/blob/81f5d63218851f90bd83c1263d9a427db84d6082/django/core/cache/__init__.py#L65
property] and the wrapped `pylibmc.Client` instances are created in
`PyLibMCCache._cache`.
You might want to investigate if `pylibmc.ThreadMappedPool` does anything
different since it looks like it
[https://stackoverflow.com/questions/12420007/pylibmc-assertion-ptr-query-
id-query-id-1-failed-for-function-memcache solved a similar issue].
#11331 and #5133 might also be related.
--
Ticket URL: <https://code.djangoproject.com/ticket/25824#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4dedb52477acce932eca39de90a324e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
