-
Notifications
You must be signed in to change notification settings - Fork 120
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
sql.mysql.JdbcMysqlJ8IntegrationTests: pooledConnectionTest failed #1695
Comments
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (0440272), this test passed in one build (https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory/actions/runs/6868024506) and failed in another build (https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory/actions/runs/6868024506). |
|
Looks like a 502 brought the refresh algorithm down. |
I think we can fix this by increasing the default timeout to connnect from 30 seconds to 45 seconds. There are two timeouts that interact with each other:
At the moment both are set to 30 seconds. Which means that the test will fail if the first refresh attempt fails. This is a timeline of what happens:
If we change the default connect timeout to 45 seconds, then the tests will be able to try a second refresh attempt without failing. This is the timeline of events if the connect timeout is set to 45 seconds:
Increasing the connect timeout will not significantly impact the number of refresh requests sent to the server. |
Note: #1535 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: 0440272
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory/actions/runs/6868024506
status: failed
The text was updated successfully, but these errors were encountered: