Intro / Busy loop and blocking threads on 1.2.5
mdagosta at stumbleupon.com
Mon May 5 22:43:09 UTC 2008
The latter - both pegging the CPU and not accepting new connections. This only
happens every couple of days, but I can notice any other symptoms that are
> Is memcached simply not accepting new connections and idling, or is it
> pegging the CPU and not accepting new connections?
> Michael D'Agosta wrote:
>> New to the list - hi people. I was reading a thread from April:
>> It seems that during busy times, one of our memcached instances will
>> stop accepting new connections; when I run telnet host port, I don't get
>> a prompt. It's MC 1.2.5 on CentOS 4.6 w/ libevent 1.1a. We didn't
>> compile in threading before, so I'm giving that a test drive as I type.
>> Did anyone discover solutions or workarounds to the problem?
>> Thanks in advance,
More information about the memcached