Expected client behavior after CLIENT REPLY OFF
#2616
Yury-Fridlyand
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After sending
CLIENT REPLY OFF
orCLIENT REPLY SKIP
server stops replying, but keeps receiving and processing commands. Currently, all clients don't work properly, because all promices/futures get timed out. If we leave them unawaited we aren't guaranteed that they ever executed (and it also causes code validation issues). If we await for them, but ignore errors - client gets locked on every command until timeout; the code becomes ugly as well.Things to consider:
CLIENT REPLY OFF
in transaction handled incorrectly valkey#1268)?CLIENT REPLY ON
Beta Was this translation helpful? Give feedback.
All reactions