Note that it could also be that your webapp's threads were all just stuck
waiting to time out on one node. Depending on the client you're using, how
your app is written, it may appear that everything is 'offline', but it's
really just that your app is spending a large amount of time waiting for
Hey,
You're saying the process was just suspended and you resumed it with a
signal? Or did it crash and you had to restart it?
I don't recall any major bugs, but that version is very old (Dec 2013), so
support will be limited.
-Dormando
On Mon, 30 Oct 2017, satoshi fujioka wrote:
> Hi.
> We
Hi.
We are running 16 memcached with Tomcat's web application as a client.
Suddenly memcached hunged up at 11 o'clock on October 22, 2017.
When an event occurs, all web applications that access memcached
stopped responding.
This event was resolved by resuming the memcached process, Are there
