TB-124 Add pgpool connection manager #243
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
….com/jembi/platform into TB-124-add-pgpool-connection-manager
….com/jembi/platform into fix-hapi-JDBC-connection-issue
Fix hapi jdbc connection issue
….com/jembi/platform into TB-124-add-pgpool-connection-manager
bradsawadye
approved these changes
Jul 27, 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.
In order to better manage the underlying connections that hapi-fhir makes to postgres, I introduced Pgpool as an intermediate between hapi-fhir and postgres to better manage connections.
The reason being that while under load I found that hapi-fhir's service begins to degrade and throws errors of being unable to obtain a connection to postgres after a 30s timeout. Also on postgres side I found that it reached its max capacity of client connections. Finally, it seems like hapi-fhir will open a connection to postgres but it will idle indefinitely despite making more requests to postgres for new connections.