BigQuery QueryJob.result() ConnectionError now retried at poll level

TL;DR

If BigQuery polling jobs fail intermittently with ConnectionError in serverless or GKE environments, upgrade google-cloud-bigquery past the May 2024 fix so polling-level retries kick in.

Steps

1. If BigQuery polling jobs fail intermittently with ConnectionError in serverless or GKE environments, upgrade google-cloud-bigquery past the May 2024 fix so polling-level retries kick in. Agents running long BigQuery queries should wrap result() with their own timeout and retry policy anyway: transient network blips in GCP are normal, and the SDK's retries have layers you need to understand to debug hangs.

When to use

You are seeing this: Agents running long BigQuery queries should wrap result() with their own timeout and retry policy anyway: transient network blips in GCP are normal, and the SDK's retries have layers you need to understand to debug hangs. Use this skill when you run into "BigQuery QueryJob.result() ConnectionError now retried at poll level".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: google-cloud-bigquery 3.18.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue googleapis/python-bigquery#1929 (closed): on google-cloud-bigquery 3.18.0, QueryJob.result() in Cloud Functions and GKE intermittently died with requests.exceptions.ConnectionError that was never retried. Maintainer tswast reproduced it and shipped PR #1930: retries now also apply at the isjobdone polling level, so a connection reset while waiting for a query gets retried even after API-level retries are exhausted. The reporter confirmed the quick fix. Safe even for non-idempotent jobs because restart only happens on confirmed job failure.

Verified resolution: If BigQuery polling jobs fail intermittently with ConnectionError in serverless or GKE environments, upgrade google-cloud-bigquery past the May 2024 fix so polling-level retries kick in. Agents running long BigQuery queries should wrap result() with their own timeout and retry policy anyway: transient network blips in GCP are normal, and the SDK's retries have layers you need to understand to debug hangs.

Source URL: https://github.com/googleapis/python-bigquery/issues/1929