CDC Replication Error: MySqlDbSet.getUUID() NullPointerException

[VladimirDVV]

Hello! I encountered an error when replicating MySQL in ClickHouse using CDC. The sync fails with a NullPointerException related to the CDC state.
Error Message:
Failure in source: incumbent CDC state is invalid, reason: java.lang.NullPointerException: Cannot invoke "io.debezium.connector.mysql.grid.MySqlDbSet.getUUID()" because "other" is null
Environment:

Source: MySQL
Destination: ClickHouse
Sync Mode: Incremental / CDC

mysql___clickhouse_logs_8_txt.txt

[Aaron ("AJ") Steers (aaronsteers)]

Hi VladimirDVV, thank you for reporting this issue!

I've reviewed your logs and can see the error clearly. The sync fails during the CDC read phase with:

io.airbyte.cdk.ConfigErrorException: Incumbent CDC state is invalid, reason:
java.lang.NullPointerException: Cannot invoke "io.debezium.connector.mysql.gtid.MySqlGtidSet$UUIDSet.getUUID()" because "other" is null

What's happening: The source-mysql connector is validating the stored CDC state (GTID set) against the current MySQL server's GTID set, but encounters a null reference when comparing UUID entries. This typically occurs when the MySQL server's GTID topology has changed since the last successful sync — for example, after a failover, replica topology change, or GTID purge on managed MySQL (YandexCloud in your case).

Possible workaround: You can try resetting the connection state for this sync to force a full CDC re-sync:

Steps to reset CDC state

1. Go to your connection in the Airbyte UI
2. Navigate to the stream settings
3. Use the "Clear data and reset" option for the affected stream(s)
4. Re-run the sync

This will clear the stored CDC state and start fresh, which should bypass the invalid GTID comparison.

To help the team investigate further, could you share a few additional details?

• Are you running Airbyte Cloud or OSS (self-hosted)? If OSS, which version?
• Has your MySQL instance recently undergone any infrastructure changes (failover, migration, replica changes)?
• Was this sync previously working successfully, or is this the first attempt?

Please ensure you mask or remove any sensitive information (API keys, passwords, tokens, connection strings) before sharing any additional logs or configuration.

This issue has been escalated to the internal team for investigation: https://github.com/airbytehq/oncall/issues/11532

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

This message is generated from Devin.ai (internal session link).

[VladimirDVV]

Here are the details regarding my environment:

Airbyte version: I am running Airbyte OSS (self-hosted). Installed via abctl (version v0.30.3-windows-amd64) on Docker Desktop 4.61.0.
Infrastructure changes: No recent changes. This is a restored backup of a MySQL database used specifically for testing purposes.
Previous status: This is the first attempt to run this sync. It has never worked successfully before.
mysql___clickhouse_logs_9_txt.txt
mysql___clickhouse_logs_10_txt.txt

[msbrizuela]

Same Issue happened to me, also first sync with no previous CDC State, reseting didnt help, deleting stuff from

DELETE FROM state
WHERE connection_id = '24bf70c9-afe6-498d-9524-e964ccf64864';

DELETE FROM retry_states
WHERE connection_id = '24bf70c9-afe6-498d-9524-e964ccf64864';

also didnt help
i'm on Airbyte 2.0.1 selft hosted , and using mysql connector version v3.51.5
cheers