I just upgraded our memcached configuration to span across multiple
servers instead of just on the web server as we were using previously.
Our configuration went from this...

CACHE_BACKEND = 'memcached://127.0.01:11211'

To this...

CACHE_BACKEND = 'memcached://
10.0.0.1:11211;10.0.0.2:11211;10.0.0.3:11211;10.0.0.4:11211;10.0.0.5:11211/'

Apache will then run fine for an arbitrary amount of time after which
the error log will fill up (and I mean fill up, as in taking up 100%
of available disk space) with errors like this...

[EMAIL PROTECTED] mcm_buf_read():361: read(2) failed: Resource
temporarily unavailable: server unexpectedly closed connection
[EMAIL PROTECTED] mcm_buf_read():361: read(2) failed: Resource
temporarily unavailable: server unexpectedly closed connection
[EMAIL PROTECTED] mcm_buf_read():361: read(2) failed: Resource
temporarily unavailable: server unexpectedly closed connection

This is a known issue with libmemcache and I have been considering
switching to python-memcached even though it is 2x slower, but first
wanted to see if any of you have experienced this or know any
workarounds.

Thanks!
~J


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to