listen_disabled_num doesn't seem to be a likely culprit...
stats
STAT pid 11435
STAT uptime 4457974
STAT time 1417457018
STAT version 1.4.5
STAT pointer_size 64
STAT rusage_user 19038.393825
STAT rusage_system 42581.905202
STAT curr_connections 264
STAT total_connections 1572308
STAT
You may also consider an upgrade sometime...
If the conn tester doesn't pull up much, I don't know what it'd be beyond
things like spaces/newlines/invalid chars sneaking in, or items being too
large. that sort of thing. Cache::Memcached's error reporting is pretty
terrible.
I have a long list of
Comment #4 on issue 381 by tgrab...@gmail.com: Incomplete command does not
result in ERROR response
https://code.google.com/p/memcached/issues/detail?id=381
Is this a limitation which results from the way memcached is implementated?
TCP connections can be closed independently by each side.
Comment #5 on issue 381 by dorma...@rydia.net: Incomplete command does not
result in ERROR response
https://code.google.com/p/memcached/issues/detail?id=381
It's not really built to do half-close situations I think... if it detects
that it just blows out.
That might be the wrong thing to
