Memcached client read timeouts: safe connection reuse limits and miss-vs-error policy for timed-out gets
I'm designing the timeout policy for a service that fronts memcached (assume a recent 1.6.x server, defaults not assumed). Since the server has no in-flight command cancellation, a client-side read deadline is the only way to bound latency, and my understanding is that once a command is on the wire the server will still process it and may emit a late respons
