Signalling incremental snapshot failure stuck on a loop

[Dexarc Root]

Hi Folks,
I'm trying to work on a debezium connector with signalling snapshot that was working fine on previous tables. When i tried with one of the bigger tables, it failed with

[2026-01-14 05:01:49,096] ERROR [cp-server-cdc-msk-debezium-connector|task-0] Snapshotting of table comp.table2 failed. Skipping it (io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource:635)

com.mysql.cj.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request  The problem seems to be looping every 10 mins, CDC for all the tables is working fine and debezium is committing offsets to the kafka topic. Is there a way to stop this signalling and then I can modify chunk and other timeout parameters to re enable another signal.
Already tried and failed with
1. Inserting a stop signal to the signalling table for the particular table/all tables
2. Tried reducing chunk size from 10000 to 1024 and restarted the connector
3. Tried removing signalling parameters entirely to force only cdc to eradicate the error

[jiri.p...@gmail.com]

Hi,

can you please try to exted the session timeout setting for MySQL server?

Jiri

[Dexarc Root]

Hi

I think the session timeout is more than enough on the connector end and i have also tweaked the timeouts from DB side.

"database.initial.statements": "SET SESSION wait_timeout=28800;SET SESSION interactive_timeout=28800;SET SESSION net_write_timeout=7200;SET SESSION net_read_timeout=7200;SET SESSION lock_wait_timeout=7200;SET SESSION innodb_lock_wait_timeout=7200;SET SESSION max_execution_time=7200000000",