Releasing connections on allowed empty results when not in a transaction #3
Conversation
This file contains hidden or 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 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.
Subject pretty much sums up what this pull request is about - we were seeing apps and tests that talk to mysql through alien-node-mysql-utils hang after a point & were able to mediate the issue by increasing the number of connections. With this change applied we are able to reduce the number of connections and do not see the hanging behavior (basically just copied the "if not in a transaction release connection" logic from the non-empty result else block). Wasn't sure if bumping the version would be appropriate in this PR, but figured it wouldn't hurt to include as well.