forked from redis-rs/redis-rs
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Merge from upstream #154
Closed
Closed
Merge from upstream #154
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
barshaul
force-pushed
the
fix_multi_node_retry
branch
3 times, most recently
from
June 10, 2024 13:43
af2b318
to
3cd6fe4
Compare
barshaul
force-pushed
the
fix_multi_node_retry
branch
from
June 10, 2024 16:52
e3c9ba8
to
49a2db1
Compare
Now after merging scan and pubsub it might have some breaking changes - please rebase over our repo and test, and check if changes needed. |
barshaul
force-pushed
the
fix_multi_node_retry
branch
3 times, most recently
from
June 26, 2024 11:38
5c47d9b
to
2088795
Compare
barshaul
force-pushed
the
fix_multi_node_retry
branch
from
June 26, 2024 13:50
9495b2e
to
45015d2
Compare
This fixes a situtation where a multi-node request is sent after a disconnect, and is repeatedly being sent to the old, disconnected connection. This is caused by multi-node requests being routed with a specific connection, instead of looking for a new connection after a disconnect. amazon-contributing#144
This makes it easy to add new variables to the tests without requiring large modifications.
Async cluster connections now can handle request errors even when the request shouldn't retry. Before this change, topology refreshes and reconnects only happened on retries. This change ensures that they will happen regardless of retries.
This allows us to find errors that aren't visible in stdout/stderr.
barshaul
force-pushed
the
fix_multi_node_retry
branch
from
June 26, 2024 15:03
00c028b
to
4776cd7
Compare
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.
Including: