soma chandra sekhar attaluri
11/26/2025, 6:32 PMsoma chandra sekhar attaluri
11/26/2025, 7:09 PMEduardo Ferreira
11/26/2025, 8:50 PMsoma chandra sekhar attaluri
11/27/2025, 3:53 AMSalman Siddiqui
11/27/2025, 5:13 AMSalman Siddiqui
11/27/2025, 5:13 AMGuy
11/27/2025, 5:15 AMRussell Tang
11/27/2025, 5:16 AMChanakya Pendem
11/27/2025, 7:05 AMKothapalli Venkata Avinash
11/27/2025, 7:54 AMKothapalli Venkata Avinash
11/27/2025, 1:45 PMKothapalli Venkata Avinash
11/27/2025, 2:11 PMsoma chandra sekhar attaluri
11/27/2025, 5:20 PMsoma chandra sekhar attaluri
11/27/2025, 5:25 PMsoma chandra sekhar attaluri
11/27/2025, 6:46 PMIshan Anilbhai Koradiya
11/27/2025, 7:08 PMSlackbot
11/27/2025, 10:17 PMRenu Fulmali
11/28/2025, 9:47 AMFabrizio Spini
11/28/2025, 11:06 AMpostgresql:
enabled: false
extraVolumes:
- name: postgres-ssl-cert
configMap:
name: postgres-ssl-cert
extraVolumeMounts:
- name: postgres-ssl-cert
mountPath: /etc/ssl/certs/postgres-ca.crt
subPath: ca.crt
extraEnv:
- name: POSTGRES_TLS_ENABLED
value: "true"
- name: POSTGRES_TLS_DISABLE_HOST_VERIFICATION
value: "true"
- name: SQL_TLS_ENABLED
value: "true"
- name: SQL_TLS_DISABLE_HOST_VERIFICATION
value: "true"
global:
auth:
enabled: false
resources:
worker:
jobs:
requests:
memory: "6Gi"
limits:
memory: "8Gi"Kothapalli Venkata Avinash
11/28/2025, 1:29 PMJavier Molina Sánchez
11/28/2025, 1:56 PMjava.lang.NullPointerException: Cannot invoke "io.debezium.connector.mysql.gtid.MySqlGtidSet$UUIDSet.getUUID()" because "other" is null. I've enabled GTID in mysql, reboot the machine, did a full-load and then perform the blue/green deployment. Can you help me understand why Airbyte is not able to connect again?David Backx
12/01/2025, 7:12 AMeadFromSource: exception caught
java.lang.IllegalStateException: Source process is still alive, cannot retrieve exit value.
The source is a MSSQL database and the destination is S3. It all started when i had wrong permissions on the database and when that was fixed i started getting these errors. Its reading almost every try between 300MB-370MB. What could be the issue?Neeraj N
12/01/2025, 7:56 AMSalman Khan
12/01/2025, 8:06 AMFabrizio Spini
12/01/2025, 8:35 AM[Bug]: MySQL CDC: Record Duplication Due to Incorrect Offset Restart After Debezium Connector Failure (Error 1236)
**Airbyte Version:** 2.0.1
**Source Connector:** MySQL CDC (Debezium)
**Destination Connector:** BigQuery
**Sync Mode:** Change Data Capture (CDC)
**Target Write Schema:** Append
### :ladybug: Bug Description
When a MySQL CDC sync job (Run 1) fails *after* starting the data emission, the subsequent job (Run 2) incorrectly restarts from the **initial binlog offset of Run 1** instead of the last committed offset. This leads to the re-processing and re-writing of records already sent to the BigQuery destination, causing **data duplication** due to the **Append** write mode.
### Steps to Reproduce
1. Configure a **MySQL CDC Source Connector** (Airbyte 2.0.1) syncing to a **BigQuery Destination** using the **Append** write mode.
2. Start **Run 1** (sync) which successfully begins streaming from a specific position:
```log
2025-11-30 11:46:50 source ERROR : Requesting streaming from position filename: db05-slave.087542, position: 87056536
3. Force Run 1 to fail shortly after it starts streaming, specifically triggering the Debezium/MySQL Error 1236 (replica ID conflict).
* The failure log excerpt:
log
2025-11-30 11:46:56 source ERROR blc-db05-slave.bravofly.intra:3306 i.d.p.ErrorHandler(setProducerThrowable):52 Producer failure io.debezium.DebeziumException: A replica with the same server_uuid/server_id as this replica has connected to the source; the first event 'db05-slave.087542' at 87056536... Error code: 1236; SQLSTATE: HY000.
4. Verify that BigQuery received records before Run 1 terminated.
5. Correct the failure cause (e.g., resolve the server ID conflict) and start Run 2.
6. Observe the Run 2 log: The connector logs immediately confirm it is restarting from the exact same binlog position where Run 1 started (db05-slave.087542, position=87056536), demonstrating the incorrect offset retrieval:
* Run 2 Log excerpt:
log
2025-11-30 12:11:19 source INFO DefaultDispatcher-worker-3#global-round-1-create-partitions i.a.c.r.c.CdcPartitionsCreator(run):144 Current position 'MySqlSourceCdcPosition(fileName=db05-slave.087542, position=87056536)' does not exceed target position 'MySqlSourceCdcPosition(fileName=db05-slave.087546, position=19566958)'.
7. Check the BigQuery table: the initial batch of records (those processed between Run 1 start and failure) is duplicated.
### Expected Behavior
The subsequent job (Run 2) should resume from the last binlog offset that was successfully confirmed (committed state) by the BigQuery destination connector. This ensures that records already written to the target are not re-processed and duplicated.```
do you already have a similar bug reported for this behaviour?Piyush Shakya
12/01/2025, 9:33 AMAswin
12/01/2025, 10:13 AMPiyush Shakya
12/01/2025, 3:34 PMLucas Segers
12/01/2025, 4:24 PMChris Dahms
12/01/2025, 5:06 PM