Comment #1 on issue 384 by [email protected]: memcached refuse to recv
data if the client send too much data without recving
https://code.google.com/p/memcached/issues/detail?id=384
I'm *pretty* sure this affects all versions. I remember very old versions
definitely being affected by this.
What changed are the clients.. some of them were updated to allow reading
some response data if sending starts to fail. There's not much the daemon
can do in this situation (especially for things like binprot where it has
to immediately write onto the wire). Are you accidentally testing different
versions of libmemcached as well?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
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.
