Bug fix: Mark connection as not good when error on cancellation confirmation #68
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
added 3 commits
November 14, 2022 14:15
|
@microsoft-github-policy-service agree company="ozontech" |
|
@apoorvdeshmukh @stuartpa @JyotikaGargg Hi! Sorry for pinging you guys. Any chance you can take a look at this one? Really looking forward for this fix to be merged and released, it will help me a lot! Thank you in advance! |
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.
This pr fixes bug when we were not able to get cancelation confirmation but connection is not marked as bad and returns to pool, so next time this connection is taken from pool, we get the same error instead of opening new good connection
Example:
r, err := db.QueryContext(ctx, query) <- context expired, then we got cancelation confirmation error
...
r, err := db.QueryContext(ctx, query) <- we get same error because we are still using bad connection instead of opening new one
same as denisenkom#773