Marking it as query, but it affects any component that uses go-couchbase or gomemcached.
When a gomemcached Get() ends prematurely (the most likely cause being a golang timeout),
client/transport.go:getResponse() leaves the response structure uninitialized, which means that it has a 0 status.
This is not picked as fatal, and the connection gets eventually reused, reading incorrectly, data left behind on the wire.
|For Gerrit Dashboard: MB-42555|
|139570,1||MB-42555 mark connections as unusable on golang / os socket errors||mad-hatter||gomemcached||Status: MERGED||+2||+1|
|139715,2||MB-42555 mark connections as unusable on golang / os socket errors||master||gomemcached||Status: MERGED||+2||+1|