How about cmemcache [1], maybe it's a problem with tummy's pure-
Python memcache API, or maybe not.
[1] http://gijsbert.org/cmemcache/index.html
2006-12-24 1:02 Osso
Hello,
For our website (http://www.curse-gaming.com), we are using a pool
of 8
servers.
The problem is when a ser
It does.
The problem is that the socket is in blocking mode so when a server
goes down the client waits at the socket.connect for a lot of time and
that for each instance of python. Once the connection times out the
server is marked as down for 30s, so the client works for 30s then
stops again (
On 12/23/06, Osso <[EMAIL PROTECTED]> wrote:
For our website (http://www.curse-gaming.com), we are using a pool of 8
servers.
The problem is when a server goes down, or more precisely when one the
memcached instances goes down, it crashes the whole website.
Hmm, it'd be helpful to see a traceb
Hello,
For our website (http://www.curse-gaming.com), we are using a pool of 8
servers.
The problem is when a server goes down, or more precisely when one the
memcached instances goes down, it crashes the whole website.
We are actually using a modified version of the tummy's python
memcached co
4 matches
Mail list logo
