Memcached.py (the client library) will mark a server as dead, and then continue to use the remaining servers. The tuple error seems to be in how the error is passed to mark_dead: the client code is inconsistent about what part of the failure exception it uses.
Not pooling your cache won't help here: the client library always thinks of the servers as a pool. If you only have one server, you'll still be running all the same code, and if for some reason that server becomes unreachable, you'll likely have the same error in the client library, plus you won't have any cache left! --Ned. http://nedbatchelder.com [EMAIL PROTECTED] wrote: > I'm not sure if this is a question about Django's implementation of > Memcached, but I figure I'll start here... > > I've got three memcached servers running as a shared pool, and I my > settings file looks like this: (web1-3 are hostnames) > > CACHE_BACKEND = 'memcached://web1:11211;web2:11211;web3:11211/' > > What happens if I lose one of the servers in my pool? Is this > something that Django works around, or is Memcached responsible? > > I ask because it's happening to me right now, but I've only seen one > error message about it. Specifically, I got the error on line 513 of > memcache.py that the "tuple index is out of range" when it tries a > self.mark_dead() method. > > It's making me rethink the idea of pooling my cache... > > Scott > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
