RUST-954 Pin connections for transactions when connected to a load balancer #461
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
awitten1
pushed a commit
to awitten1/mongo-rust-driver
that referenced
this pull request
Sep 21, 2021
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.
RUST-954
Transaction connection pinning follows the same rules as mongos pinning for sharded transactions, so this CL augments that machinery to be able to track a
PinnedConnectionHandle.The load balancer spec requires the drivers to track whether a connection is checked out for a cursor vs a transaction vs anything else for the purpose of augmenting the
WaitQueueTimeoutErrormessage; however, the Rust driver does not support wait queue timeouts, so I've omitted that tracking.