Update DB connection pooler config #3333
Merged
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.
Resolves #3316
Updates the following database connection pooler configs, with the goals of reducing the number of idle connections we hold on to, and reducing the likelihood that a server fails to ever connect to a database after an auto-deploy.
Testing instructions
make ssh target=db
psql -U sidewalk -d sidewalk
idleMaxAge
to be just a few seconds and you keep running this query, you can watch how the number of connections increases when you load a page, and then goes back down tominConnectionsPerPartition
afteridleMaxAge
.The retry configs will be a lot easier to test on the test servers!
Things to check before submitting the PR