SetQ, AddQ, and ReplaceQ calls return a response on success
ScottMansfield opened this issue · comments
Under high enough load, the client will squash multiple sets, adds, and replaces (among others) into pipelined requests to the server. When the server gets a SetQ request, it is incorrectly setting the response to be the not-quiet version (e.g. SetQ becomes Set) while processing the request.
All places where the original request's Quiet field is altered while processing a request should be changed to either cache it or not do so.
CC @vuzilla