PR #3073 (0.9.9 patch) never forward-ported the 159 retryable again and setQueryTimeout does not set max_execution_time on main/0.10.0
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
Start by comparing ServerException.discoverIsRetryable() and Statement.setQueryTimeout() on main with their v0.9.9 behavior. Reproduce a query exceeding max_execution_time and inspect system.query_log; done means timeout code 159 is not retried and setQueryTimeout also applies the server-side limit.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
PR #3073 ("Makes 159 Execution Timeout not retriable & make setQueryTimeout set proper setting"),
which closed #3074 the 0.9.9 patch tracking issue for #2637, was merged with base v0.9.9,
not main. It was never forward-ported, so both of its fixes are absent from v0.10.0 and from
main today (@ a7fd189c):
1. 159 TIMEOUT_EXCEEDED is retryable again. ServerException.discoverIsRetryable():
| ref | case 159: present |
|---|---|
| v0.9.8 | yes |
| v0.9.9 | no (fixed by 9378ba09f2) |
| v0.10.0 | yes |
main @ a7fd189c |
yes (line 62) |
2. Statement.setQueryTimeout() still does not set max_execution_time. On main,
queryTimeout is used only as a client-side future.get(timeout, SECONDS) — the client stops
waiting but the server keeps executing the query. v0.9.9 additionally sets the server setting.
This is the original symptom reported in #2637, which is still open.
Steps to reproduce
- Set
max_execution_timelow on the user's settings profile (e.g. 30s), or call
setQueryTimeout()on 0.9.9 where it maps to that setting. - Execute a query that reliably exceeds it.
- Observe the client re-executing the identical query up to
retrytimes — one
WARN ... Retrying.per attempt. Insystem.query_logthe same query text appears N+1 times,
each ending inExceptionWhileProcessingwithexception_code = 159.
Environment
- Cloud
- Client version: 0.9.8 (also reproduces on v0.10.0 and
main@a7fd189c; fixed only on v0.9.9) - Language version: Java 21 (Temurin 21.0.6)
- OS: Linux (container)
- Lenguaje dominante
- Java
- Estrellas
- 1.6k
- Forks
- 637
- Merge medio
- 2 d 12 h
- PR fusionados (30 d)
- 28
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ClickHouse/clickhouse-java
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ClickHouse/clickhouse-java#3143 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
ClickHouse/clickhouse-java#3111 ·
-
area:data-type bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ClickHouse/clickhouse-java#3098 · 1 comentario ·
-
bug client-api-v2 test
Dificultad 2/5 1-3 horas Aptitud para principiantes 92/100
ClickHouse/clickhouse-java#3076 ·
-
area:sql-parser bug client-v1
Dificultad 1/5 1-3 horas Aptitud para principiantes 92/100
ClickHouse/clickhouse-java#3066 ·
Todos los issues de ClickHouse/clickhouse-java
Issues similares
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Cannot differ own consent and managed consents in My Consents view and detailed consent view. Abierto1.0.0-alpha2 Type/Improvement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
wso2/dpdp-accelerator#272 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100