-
Notifications
You must be signed in to change notification settings - Fork 732
Closed
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
We recently encountered java.net.SocketTimeoutException
with java-bigquery after we increased the server side timeout for one of the BigQuery REST services. This causes the server delay the response for long running queries (basically it waits and polls on the server side, but from the client API point of view we may not get the HTTP response for the mentioned amount of time, which we defines as 60000 ms, but it could be quite a longer time too)
Related Bug: googleapis/java-bigquery#2248
Is there a way we can increase the transport layer timeout? Or would you suggest any other settings/configuration to be used when the REST API is expected to take a long time to return? Please note that the above mentioned issue is an intermittent one.
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.