Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question : IdleTimeOut Best Practice #2190

Open
Yunsik-Choi opened this issue Apr 5, 2024 · 0 comments
Open

Question : IdleTimeOut Best Practice #2190

Yunsik-Choi opened this issue Apr 5, 2024 · 0 comments

Comments

@Yunsik-Choi
Copy link

Yunsik-Choi commented Apr 5, 2024

⏳idleTimeout
This property controls the maximum amount of time that a connection is allowed to sit idle in the pool. This setting only applies when minimumIdle is defined to be less than maximumPoolSize. Idle connections will not be retired once the pool reaches minimumIdle connections. Whether a connection is retired as idle or not is subject to a maximum variation of +30 seconds, and average variation of +15 seconds. A connection will never be retired as idle before this timeout. A value of 0 means that idle connections are never removed from the pool. The minimum allowed value is 10000ms (10 seconds). Default: 600000 (10 minutes)

I wonder IdleTimeOut Best Practice.
Why HikariCP set Default : 600000 ?
Is there IdleTimeOut Formula?
Please recommend IdleTimeout value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant