We're running memcached 1.2.2 on linux, and using windows 2003 server clients. I noticed some of our memcache servers stopped responding to stats queries, and saw we have more client connection attempts than memcache was configured to handle. Using putty I could not get a stats query to respond from these servers, it would simply hang. Also a ruby script I wrote to get stats would not fail, it would just hang forever.
This has really bad side effects on our apps, where it can actually lock up request threads and cause server timeouts. Why does memcache not give back an error immediately if the connection is not available, or is this a sockets issue on windows? I've bumped up the connection limit on the server side, but I would like to know if there is something else I can do to ensure the client never gets hung, even if memcache is at its max connection limit. Would a memcache version upgrade fix this particular problem? Thanks.
