Hey, http://memcached.org/timeouts - sounds like you've already done some tcp dumping, so checking the stats as mentioned in here and running the test script a bit should illuminate things a bit.
On Fri, 21 Nov 2014, [email protected] wrote: > A couple months ago, we moved our memcached nodes from a dedicated VM to > having one each on our four baremetal web servers (mod_perl). > Since we moved, we've been seeing 10-20 failures per hour across our entire > environment, where $c->set returns false. > > I just spend some time with tcpdump and wireshark watching the memcached > traffic over port 11211. The keys that are failing are *not* in the > tcpdump, so I'm thinking Cache::Memcached has lost a connection or got a > non-functioning socket somehow? > > Does anything in this scenario give anybody any ideas of what might be going > wrong? > > Each memcached node has about 250 connections at any given time and is > handling up to 350 gets/sets per second. The load on these webservers is > around "1" (eight-core boxes). Their total network traffic is about 30 > Mb/sec, and memcached traffic is about 3 Mb/sec. There's nothing in > memcached's logs. > This is debian 6 (squeeze). > > $ dpkg -l | grep memcached > ii libcache-memcached-perl 1.29-1 > Perl module for using memcached servers > ii memcached 1.4.5-1+deb6u1 > A high-performance memory object caching system > > -- > > --- > 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. > >
