Uses a scoped session for scheduler objects. #3634
Merged
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
…leaning up connections rather that just closing them.
wssheldon
approved these changes
Jul 31, 2023
forestmonster
approved these changes
Jul 31, 2023
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.
I believe our main issue is because we are using
session.close()instead ofsession.remove()and because each scheduled run is in it own thread we should be usingscoped_sessionas well. This seems to work fine in my tests, but will be hard to tell for sure until we do a deployment with this code to see if it actually resolves our connection issues.https://docs.sqlalchemy.org/en/13/orm/contextual.html#contextual-thread-local-sessions