You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2019. It is now read-only.
user: db_username,
password: db_password,
host: db_host,
port: db_port',
database: db_schema,
max: 10, // set pool max size to 10
min: 0, // set min pool size to 0
idleTimeoutMillis: 10000, // close idle clients after 10 seconds
softIdleTimeoutMillis: 10000,
evictionRunIntervalMillis: 10000
No matter what we change the values of the last 5 items to (I added the last 2 after no love on the idleTimeoutMills by itself) there is always 1 idle connection to the database left open. Days and days go by and there is still one idle connection left open to the database server. Is there a way to have the pool clean up idle connections down to 0?
Here's the code we're using, Database.connections[host].connection is as above.
No matter what we change the values of the last 5 items to (I added the last 2 after no love on the idleTimeoutMills by itself) there is always 1 idle connection to the database left open. Days and days go by and there is still one idle connection left open to the database server.
How are you checking? Are you sure it doesn’t come from somewhere else?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No matter what we change the values of the last 5 items to (I added the last 2 after no love on the idleTimeoutMills by itself) there is always 1 idle connection to the database left open. Days and days go by and there is still one idle connection left open to the database server. Is there a way to have the pool clean up idle connections down to 0?
Here's the code we're using,
Database.connections[host].connection
is as above.Pool init:
Queries:
The text was updated successfully, but these errors were encountered: