Opened 9 years ago

Last modified 9 years ago

#25824 closed Uncategorized

Assertions in libmemcached when multiple django.core.cache.backends.memcached.PyLibMCCache backends used — at Version 3

Reported by: Michał Łowicki Owned by: nobody
Component: Uncategorized Version: 1.8
Severity: Normal Keywords:
Cc: Florian Apolloner Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Michał Łowicki)

We're running Django 1.8.3 via uWSGI with threads enabled (uWSGI 2.0.11.5, configuration - https://gist.github.com/mlowicki/9a5042b5411537a51bbf).

When two backends using 'django.core.cache.backends.memcached.PyLibMCCache' are added and are used (each box is handling at least hundreds requests per second) then in uWSGI logs we're seeing lots of https://gist.github.com/mlowicki/a8b3dbd98f32dc40c4eb and application is misbehaving throwing 500s. When launched in second datacenter with much less threads then problem is much smaller but still exists (uWSGI configuration - https://gist.github.com/mlowicki/cbd18c689c3e2f838bf0)

Tried with pylibmc 1.4.1 and 1.5.0. Running on Debian Wheezy.

Change History (3)

comment:1 by Michał Łowicki, 9 years ago

Description: modified (diff)

comment:2 by Tim Graham, 9 years ago

It's not clear to me that Django is at fault. Can you provide any details about that?

comment:3 by Michał Łowicki, 9 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top