-
Notifications
You must be signed in to change notification settings - Fork 43
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
Extremely slow queries with timeouts can incapacitate the pool #20
Comments
Do you expect A to be killed in case of timeout? |
Given the PR above, I think yes that is a decent approach, however I'm happy to be convinced otherwise. |
@seriyps this is nice in pooler, too:
I and others kept arguing for something like that to be added to poolboy, but I don't know if they ever did. It makes a lot of sense for an expensive resource to not be 'returned' right away when you have a burst of traffic. |
Agreed, I think the suggested 'kill on timeout' is sensible tradeoff, as long as the connection works within the requiested timeframe it can keep on living but connections that time out have to die, but at least the death is quick and merciful. |
Running extremely slow querries, that time out can result in the entire pool becoming unusable. So far it looks like the following happens:
We have:
A pool with the workers [A, B, C]
This has been verified by:
The text was updated successfully, but these errors were encountered: