i've experienced an issue where restarting the memcached server can cause an issue with the pylibmc backend
the wonderful error reporting is this:
File "/var/www/sites/MyApp.In-virtualenv/local/lib/python2.7/site-packages/dogpile.cache-0.4.0-py2.7.egg/dogpile/cache/region.py", line 393, in delete self.backend.delete(key) File "/var/www/sites/MyApp.In-virtualenv/local/lib/python2.7/site-packages/dogpile.cache-0.4.0-py2.7.egg/dogpile/cache/backends/memcached.py", line 159, in delete self.client.delete(key) _pylibmc.UnknownReadFailure: error 7 from memcached_delete(group:id:56): UNKNOWN READ FAILURE
This is totally an issue with pylibmc : they've raised the error and have some meager reporting
I just wanted to put this on the radar that errors like this happen -- as they will cause a webpage to error- out. I'm wondering if there should be a config option to catch and suppress errors like this.