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
one down node to timeout.

One solution to this is to implement a circuit breaker pattern

Hope that helps!

Matt

On Mon, Oct 30, 2017 at 9:25 AM dormando <[email protected]> wrote:

> 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 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
> > already known problems?
> > Please tell me if there is information available when analyzing.
> >
> > Describe the current statistical information.
> >
> > Memcache Version        1.4.16
> > Start Time            2017/10/22 14:08:56
> > Uptime                4 days, 5 hours and 49 minutes
> > Memcached Server Version    1.4.16
> > Used Cache Size            79.4 MBytes
> > Max Cache Size            1.0 GBytes
> > Current Connections Count    250
> > Total Connections So Far    588
> > Flush CMD count            28
> > Get CMD count            388652096
> > Set CMD cunt            8367177
> > Items Evicted So Far        0
> > Bytes Read So Far        10.8 GBytes
> > Bytes Written So Far        1009.4 GBytes
> > Threads                4
> >
> > Discribe software version we used.
> >
> > Apache    2.2.34
> > Tomcat    7.0.79
> > JDK    8u144
> > memcashd    1.4.16
> > kernel    2.6.32-696.6.3.el6.x86
> >
> > Regards.
> >
> > --
> >
> > ---
> > 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/d/optout.
> >
>
> --
>
> ---
> 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/d/optout.
>

-- 

--- 
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/d/optout.

Reply via email to