This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
Fix reading from replicas in pipelined commands #471
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We fail to send the
READONLYcommand to replicas when running commands inside a pipeline, which results in an increased latency as the server will respond with an unneededMOVEDmessage forcing us to retry the command.We move the sending of the
READONLYcommand to the connection creation itself, since at that point we already know if we're connecting to a replica or not, so we can ensure consistency on sending this command.Fixes #470