-
Notifications
You must be signed in to change notification settings - Fork 32
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
SNOW-1229299 Honor PDO Timeout Setting on Connections #170
Comments
Is there any update on this? We are seeing an issue where the PDO timeout would be helpful if respected, and would like to know if this has been addressed in the last 3 years. Thanks! |
Any update on this ? |
hi - there's been a couple releases since this issue was raised, so closing this issue for now. If it's still a problem, do comment please and I'll reopen and we can look. |
Tested just now and issue still present :( |
did some tests and it appears that this is not so well documented 😓 but apparently we can rely on various timeout settings : {"logintimeout", "300", 0},
{"maxhttpretries", "7", 0},
{"retrytimeout", "300", 0} starting from v2.0.1 and onwards, problem is that they stil don't seem to be taking effect although the driver correctly logs their altered value when using like $dbh = new PDO("snowflake:account=$account;logintimeout=3;retrytimeout=4;maxhttpretries=5", $user, $password); we're taking a look further. |
Could you please provide an estimated timeframe for the resolution? It would be greatly appreciated. Thank you. |
At this moment I can share the following updates from the dev team, hopefully clarifies some bits:
so hard to estimate the fix, because partly it works as expected (just I used unexpected values for my test), partly it really seems to be bug-ish, partly is an enhancement for e.g. chunk downloading which does not have a controllable timeout today i'll post any new information in the same thread and thank you for bearing with us ! |
This is confirmed to be a bug in the underlying libsnowflakeclient. Currently the retry timeout (or network timeout) would only work as expected when it's longer than the default timeout ( Driver team will make fix on the libsnowflakeclient side, both the timeout issue and the retry behavior for chunk downloading. |
PR (in the underlying libsnowflakeclient) snowflakedb/libsnowflakeclient#683 |
PR merged and will be released with the next version of the PHP driver, which first needs to be rebased on the new release from libsnowflakeclient which actually contains the fix. So at this very moment, I cannot confirm which PHP driver version will actually have the fixed code. Have no timeline on this at this moment but will update this thread. In the meantime, PHP driver's README has been updated with some description about the available timeout values and setting them. |
quick update: fixed libsnowflakeclient now released and we're targeting 2024 April (~end of month) to release the new PHP driver based on that. edit: fix for PHP driver based on the libsnowflakeclient fix: #376 |
fix is available with the fresh release of Snowflake PHP driver v2.0.3 |
When a new connection is established, we should honor the connection timeout value specified by the PDO driver
The text was updated successfully, but these errors were encountered: