We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands can run into a "won't ever come back" state when lettuce tries to reconnect but fails while reconnecting/re-issuing commands.
Desired behavior: Either re-issue/retry commands on each reconnect or cancel commands after the reconnect failed but not loose commands.
See #31 (comment) for details
@Kitchik: Will continue parts of #31 here. What do you think about the desired behavior?
The text was updated successfully, but these errors were encountered:
Added ClientOptions#cancelCommandsOnReconnectFailure to cancel commands when reconnect fails on protocol level.
ClientOptions#cancelCommandsOnReconnectFailure
Sorry, something went wrong.
No branches or pull requests
Commands can run into a "won't ever come back" state when lettuce tries to reconnect but fails while reconnecting/re-issuing commands.
Desired behavior:
Either re-issue/retry commands on each reconnect or cancel commands after the reconnect failed but not loose commands.
See #31 (comment) for details
@Kitchik: Will continue parts of #31 here. What do you think about the desired behavior?
The text was updated successfully, but these errors were encountered: