I don't think the problem is caused by the PHP extension at this point, since having the sockets in a CLOSE_WAIT state is most likely indicative of something in the memcached server not closing the connection after it gets a FIN. I've been monitoring memcached over the past few days, and it normally doesn't get in this state. i.e. I don't normally see ANY CLOSE_WAIT connections open. However, when it starts not responding to connection requests, it appears to be in this state where there's thousands of CLOSE_WAIT connections. Does anyone have suggestions for how I can debug this further? Memcached is not being production-ready reliable for me right now (including the weekly crash listed in the original post, which may or may not be related).
-- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
