Problem Note 70583: Reading a Google BigQuery table might take longer than normal and result in a crash or an “ERROR: During read: processStream retries exhausted”
 |  |  |  |  |
When reading data from SAS/ACCESS® Interface to Google BigQuery, the step might take longer than expected and result in either a crash or the following error message:
ERROR: During read: processStream retries exhausted: rpc error: code = Unavailable desc = error reading from server: read tcp
10.109.61.199:33152->10.109.122.30:8080: read: connection timed out
10.109.61.199:33152->10.109.122.30:8080: read: connection timed out
Only the following workarounds are available for this issue:
- Retry the query.
- Reduce the number of rows being read.
The root cause is thought to be an unexpected network or a Google BigQuery error, which results in a crash in SAS/ACCESS® Interface to Google BigQuery.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Google BigQuery | Linux for x64 | 9.42 | 9.4 TS1M7 | ||
A fix for this issue for SAS/ACCESS Interface to Google BigQuery 9.43 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/M7Z.html#70583A fix for this issue for SAS/ACCESS Interface to Google BigQuery 9.42 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/K2L.html#70583A fix for this issue for SAS/ACCESS Interface to Google BigQuery 9.41 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/H5A.html#70583
When reading larger Google Bigquery tables, random failures might occur, resulting in a crash or "connection timed out" messages.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2024-02-26 12:18:13 |
| Date Created: | 2023-12-20 07:01:49 |