-
Notifications
You must be signed in to change notification settings - Fork 12
Can we add timeout for resource acquiring? #10
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
Comments
anybody @arybczak @soareschen ? |
Sounds good to me. You can add a new configuration option to |
This is important. When our app saturates the pool, requests start backing up, memory use explodes superlinearly, and the app crashes. With a timeout, we could fail gracefully. |
There's #11, but it's abandoned. Feel free to pick it up and make it up to date if you need it, so it can be merged 🙂 |
Can we add optional timeout for resource acquiring? Not for creating but taking resource. For now pool waits for available resource infinitely that can be a reason of dead locks.
prints
And gets stuck. Of course, it's a user-code bug. But it's better to get exception than get stuck forever
I'm ready to implement it
The text was updated successfully, but these errors were encountered: