Can you get 'stats' output? What does listen_disabled_num say? Can you start memcached with -o maxconns_fast, and does that change the errors you get?
On Tue, 11 Feb 2014, Joe7 wrote: > Hi Ryan! > The client is PHP/Pecl memcached yes. > > It is actually happening before the cache would get full too, managed to > replicate it at only ~20% filled today. > It's not happening for a couple of mins after memcached restart..but later > then every minute or even every couple of seconds. > > There is quite a bit of traffic on the port usually, but will deffo try to > filter for this with ngrep and report back. > > cheers > > On Wednesday, February 12, 2014 12:36:59 AM UTC+1, Ryan McElroy wrote: > Hi, I'm not familiar with this the client errors -- but from a search, > I'm guessing that you're using the PHP memcached library? > Eg http://www.php.net/manual/en/memcached.constants.php... > Anyway, to tell what the server is actually complaining about (as opposed to > how the client is reporting back), I like to use a network dump > -- ngrep is my favorite. Can you see what the actual network traffic on the > port is like during one of these failures? That might give some > clues. > > Based on what you've said so far, he's a shot in the dark: when the server is > filing up (eg, not evicting) everything is fine, but when we > need to evict as well, things get a little slower and so either the client is > timing out or the server is having allocation trouble (I don't > know if the actually happens, which is why I want to see what's coming over > the wire). Once the client sees a few of these failure to write > (or maybe just one), it puts connecting to the server on hold for a short > time to make sure it's not contributing to the problem, and then > for this period of time you see the the temporarily disabled error (and the > client isn't actually sending traffic). The server is probably > still up at this point, the client is just failing fast. > > This theory can be confirmed or refuted with ngrep or tcpdump. > > Hope this helps! > > ~Ryan > > > On Tue, Feb 11, 2014 at 8:26 AM, Joe7 <joe7...@gmail.com> wrote: > Just to confirm: its only happening once the cache is full > > -- > > --- > 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 memcached+...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > > --- > 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 memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
