#25824: Assertions in libmemcached when multiple
django.core.cache.backends.memcached.PyLibMCCache backends used
-------------------------------+--------------------------------------
     Reporter:  mlowicki       |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  new
    Component:  Uncategorized  |                  Version:  1.8
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by mlowicki):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> 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])

New description:

 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.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/25824#comment:1>
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.0b9b80052c99bf910f68cda84fb6343a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to