Iulian
09/24/2026, 12:33 PMYuki Kakegawa
09/24/2026, 3:20 PMTatiane Corrêa
09/24/2026, 4:11 PMpod-sweeper.sh rodando no GKE e queria saber se isso já é conhecido / rastreado em algum lugar.
Ambiente: Airbyte self-hosted v1.4.1 (helm chart), cluster GKE com Image Streaming habilitado (node pool com kubelet recente).
Causa raiz: o kubelet do GKE agora injeta uma PodCondition sintética chamada ImageStreaming como conditions[0], sempre com lastTransitionTime: null — não é uma condição de ciclo de vida real, é só informativa. O pod-sweeper.sh lê conditions[0].lastTransitionTime e cai no fallback do bash ${POD_DATE_STR:-$POD_START_DATE_STR} quando está vazio — só que a string literal "null" não é tratada como vazia por esse fallback, então POD_DATE_STR acaba sendo literalmente "null", o date -d null falha, e o sweeper nunca envelhece o pod. Resultado: os pods acumulam no namespace em vez de serem limpos.
Proposta de fix :
[ "$POD_DATE_STR" = "null" ] && POD_DATE_STR=""
[ "$POD_START_DATE_STR" = "null" ] && POD_START_DATE_STR=""
POD_DATE=`date -d ${POD_DATE_STR:-$POD_START_DATE_STR} '+%s'`
Isso já é um problema conhecido? Já existe fix original ou alguma versão que resolve?Gary K
09/24/2026, 11:49 PMAltan Sener
09/25/2026, 7:51 AMIulian
09/28/2026, 8:01 AMSaved offset is not valid / oplog history lost errors — but the timing was weird: it failed almost exactly when our configured oplog retention ran out. We bumped retention from 24h to 72h thinking that'd fix it... and it just failed again 3 days later, same error.
So we dug into the actual sync logs, and found the saved resume token's timestamp was ~72 hours old — meaning the checkpoint hadn't moved forward at all in ~144 sync runs, even though those syncs were reporting success. Bumping retention just delayed the same failure, it didn't fix anything.
We ruled out a connector version bug (checked 2.0.2 vs 2.0.7, both pin the exact same CDK and Debezium versions, so no code difference there). Best guess right now is something about Debezium's heartbeat not properly refreshing the saved offset for quiet/low-write databases, especially since Airbyte restarts a fresh Debezium process every single sync instead of running it continuously.
Has anyone hit this — offset going stale in roughly the same time as your oplog retention no matter what you set it to, especially after mass-recreating a bunch of CDC connections at once? Trying to figure out if this is a known Debezium/Airbyte interaction or something specific to our setup.Rafael Felipe
09/28/2026, 11:51 AMAasim ali
09/28/2026, 8:31 PMRetry-After and retrying — the sync will resume once Gmail’s rolling quota window frees up. how to increase limitChiranga
09/28/2026, 11:40 PMLiew Tze Hao Timothy
09/29/2026, 1:23 AMreplication-job pod logs are not. Seems to be the case where the the vector label is not being injected into the replication-job pods, which is similar to this github.com/airbytehq/airbyte/issues/33068 issue. I'm currently on airbyte 1.8.5; is there any workaround or solution to this?
# -- Add extra annotations to the worker pods
podAnnotations:
vector.dev/sinks: loki
# -- Add extra labels to the worker pods
podLabels:
vector.dev/include: "true"Rajasekaran Murugesan
09/29/2026, 5:24 AM2026-09-29 04:31:20 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):136 - Docker volume job log path: /tmp/workspace/80261/0/logs.log
2026-09-29 04:31:20 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):141 - Executing worker wrapper. Airbyte version: 0.40.28
2026-09-29 04:31:20 [32mINFO[m i.a.a.c.AirbyteApiClient(retryWithJitter):172 - Attempt 0 to save workflow id for cancellation
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - ----- START CHECK -----
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/source-exchange-rates:1.2.7 exists...
2026-09-29 04:31:21 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - airbyte/source-exchange-rates:1.2.7 was found locally.
2026-09-29 04:31:21 [32mINFO[m i.a.w.p.DockerProcessFactory(create):120 - Creating docker container = source-exchange-rates-check-80261-0-lpmmh with resources io.airbyte.config.ResourceRequirements@4047ce63[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=]
2026-09-29 04:31:21 [32mINFO[m i.a.w.p.DockerProcessFactory(create):164 - Preparing command: docker run --rm --init -i -w /data/80261/0 --log-driver none --name source-exchange-rates-check-80261-0-lpmmh --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e AIRBYTE_ROLE= -e WORKER_ENVIRONMENT=DOCKER -e APPLY_FIELD_SELECTION=false -e WORKER_CONNECTOR_IMAGE=airbyte/source-exchange-rates:1.2.7 -e WORKER_JOB_ATTEMPT=0 -e AUTO_DETECT_SCHEMA=false -e AIRBYTE_VERSION=0.40.28 -e WORKER_JOB_ID=80261 airbyte/source-exchange-rates:1.2.7 check --config source_config.json
2026-09-29 04:31:21 [32mINFO[m i.a.w.i.VersionedAirbyteStreamFactory(create):100 - Reading messages from protocol version 0.2.0
2026-09-29 04:32:24 [32mINFO[m i.a.w.i.DefaultAirbyteStreamFactory(internalLog):120 - Ping response code: 504
2026-09-29 04:32:24 [1;31mERROR[m i.a.w.i.DefaultAirbyteStreamFactory(internalLog):116 - Check failed
2026-09-29 04:32:24 [32mINFO[m i.a.w.g.DefaultCheckConnectionWorker(run):110 - Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@5452dc14[status=failed,message=JSONDecodeError('Expecting value: line 1 column 1 (char 0)')]
2026-09-29 04:32:24 [32mINFO[m i.a.w.t.TemporalAttemptExecution(get):163 - Stopping cancellation check scheduling...
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 - ----- END CHECK -----
2026-09-29 04:32:24 [32mINFO[m i.a.c.i.LineGobbler(voidCall):114 -
2026-09-29 04:32:25 [32mINFO[m i.a.c.f.EnvVariableFeatureFlags(autoDisablesFailingConnections):27 - Auto Disable Failing Connections: falseGary K
09/30/2026, 5:26 AM[config_error] MySQL Timezone Configuration Issue: The sync encountered a timezone configuration issue. Please configure your database with the correct timezone as specified in the error message. For more details, refer to: <https://dev.mysql.com/doc/refman/8.4/en/time-zone-support.html>.
<https://docs.oracle.com/javase/8/docs/api/index.html?java/io/SQLException.html>Chiranga
09/30/2026, 5:57 AMYuki Kakegawa
09/30/2026, 3:12 PMQuentin Stenger
09/30/2026, 7:24 PMStuart Horgan
10/02/2026, 9:58 AMBryan Meyerovich
10/04/2026, 10:59 PMVishal Garg
10/05/2026, 7:40 AMutku yaman
10/05/2026, 8:00 AMTatiane Corrêa
10/05/2026, 12:20 PMairbyte-minio-0 com o erro
Back-off pulling image "<http://quay.io/minio/minio:RELEASE.2023-11-20T22-40-07Z|quay.io/minio/minio:RELEASE.2023-11-20T22-40-07Z>"Michael Gallivan
10/05/2026, 1:39 PMYuki Kakegawa
10/05/2026, 2:55 PMSai Saran Kalugutla
10/05/2026, 5:52 PMVishal Garg
10/06/2026, 7:26 AMYuki Kakegawa
10/06/2026, 5:59 PMSonja K
10/07/2026, 8:10 AMlars.bilek
10/08/2026, 12:24 PMTia
10/09/2026, 3:22 AMYuki Kakegawa
10/11/2026, 7:12 PMleoniejackson986
10/12/2026, 6:25 AM