Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[java-bigquery] getQueryResults does not retry a SocketTimeoutException (read timeout)

已關閉 適合新手
  • 哪裡不對？
#14,579 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@lqiu96 已經在處理了。

開始於 2026年10月20日。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
72/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
gcp, google-cloud, java
領域
api

研究方向

從 google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/BigQueryBaseService.java 中的 BigQueryBaseService.BIGQUERY_EXCEPTION_HANDLER 開始，其中 retryOn 列出了 ConnectException、UnknownHostException 和 SocketException；SocketTimeoutException 缺失。檢查該處理器在匹配之前是否會解包巢狀原因，然後使用相同的重試設定加入 read-timeout 情況（或其等價物）。完成的樣子是：bigquery 模組中的一個單元測試斷言，以 SocketTimeoutException 失敗的 getQueryResults 呼叫會被重試，而不是在第一次嘗試時拋出；gax 中斷缺陷單獨在 #12860 / PR #14578 中追蹤。

由索引模型根據 Issue 內容生成。

描述

priority: p2 type: bug

Issue Details

BigQueryBaseService.BIGQUERY_EXCEPTION_HANDLER retries ConnectException, UnknownHostException and SocketException, but not SocketTimeoutException. So when one getQueryResults call inside Job.waitFor takes longer than the HTTP read timeout, the query fails at once with BigQueryException: Read timed out, after one attempt. A read timeout on this idempotent poll is as transient as a SocketException, and the job itself is still running.

Job.waitFor calls getQueryResults with no timeoutMs, so BigQuery holds each call for up to 10 s. java-bigquery sets the HTTP read timeout to 60,000 ms by default. A poll that gets no answer within 60 s, most likely a connection that died, fails the whole query, although the job is still running and the next poll would succeed. A longer read timeout does not help a dead connection. Only a retry does.

Edited 2026-10-04: an earlier version said the default read timeout is 20,000 ms. It is 60,000 ms.

Today a second defect hides this one: gax turns the SocketTimeoutException into a thread interrupt, so the caller sees BigQueryException: java.lang.InterruptedException instead (#12860, PR #14578). With that gax fix applied, the same stall fails with Read timed out after one attempt. That remaining failure is this issue.

Expected: getQueryResults (and other idempotent reads) retries a SocketTimeoutException under the same retry settings as a SocketException.

Environment

  • OS Type and Version: macOS 26.6.2 (arm64)
  • Java Version and JDK Vendor: OpenJDK 25 (2025-09-16 LTS)
  • Deployment: a JVM server that calls BigQuery through com.google.cloud:google-cloud-bigquery, with Application Default Credentials.

Dependencies

  • Client library: com.google.cloud:google-cloud-bigquery 2.54.1 (not using libraries-bom). The handler is the same on main today.
  • Gax: gax and gax-httpjson 2.84.0
  • Auth: google-auth-library-oauth2-http 1.37.1 to 1.51.0
  • Google-Http-Java-Client: 1.47.1 to 2.2.0

Reproducer

  1. Build a BigQuery client with a short HTTP read timeout, for example 2 s, through HttpTransportOptions.
  2. Run a query, and call job.waitFor() while BigQuery holds getQueryResults (any query that takes more than 2 s).
  3. With a gax that has the #14578 fix, waitFor throws BigQueryException: Read timed out (cause java.net.SocketTimeoutException) after one attempt. With current gax, it throws BigQueryException: java.lang.InterruptedException.

The same wait with the default timeout succeeds. The handler in question is in google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/BigQueryBaseService.java:

.abortOn(RuntimeException.class)
.retryOn(java.net.ConnectException.class)
.retryOn(java.net.UnknownHostException.class)
.retryOn(java.net.SocketException.class)
主要語言
Java
星號
2.1k
分支
1.2k
平均合併
2 天 5 小時
30 天內合併 PR
128

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

googleapis/google-cloud-java 的其他 Issue

查看 googleapis/google-cloud-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。