-
Notifications
You must be signed in to change notification settings - Fork 1.9k
How to not wait connection for get command #1888
New issue
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
Comments
Experiencing the same issue where |
* ref #1888 - add disableOfflineQueue * fix flushQueuesOnError * update docs Co-authored-by: Guy Royse <[email protected]> Co-authored-by: Guy Royse <[email protected]>
@mogadanez @NathanielWroblewski dose the new |
It helps but it's still not straightforward to configure this client as an optional cache layer. Ideally the client would reconnect in parallel to returning failures on |
@mnoorenberghe sorry for the huge delay... when |
I'm using Redis as an optional cache layer.
if its failed to connect - it is wait infinitely on GET command and not
tried to set
commandsQueueMaxLength:0
is it any other way to change behavior to fail on operations if its not yet connected?
or in worse case specify operation timeout
Environment:
The text was updated successfully, but these errors were encountered: