Async cluster: reconnect after full disconnect. #100
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will allow us to early reject functions that assume that connections exist.
|
Probably type in commit msg: "After the async cluster receives a ..." - async client? |
ikolomi
approved these changes
Jan 17, 2024
After the async cluster connection receives a `ConnectionNotFound` error, it means that the cluster has no working connections, and can't refresh slots. In such a situation the cluster will try to reconnect to the initial nodes provided by the user, and afterwards refresh slots.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
aws/glide-for-redis#791
Description of changes:
After the async cluster receives a
ConnectionNotFounderror, it meansthat the cluster has no working connections, and can't refresh slots. In
such a situation the cluster will try to reconnect to the initial nodes
provided by the user, and afterwards refresh slots.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.