https://linen.dev logo
Join Slack
Powered by
```2026-06-01 16:27:04 source ERROR debezium-sqlse...
# replication-ask-ai
r
Copy code
2026-06-01 16:27:04 source ERROR debezium-sqlserverconnector-interactdbData4BI-change-event-source-coordinator i.d.r.RelationalSnapshotChangeEventSource(doExecute):193 Error during snapshot java.util.concurrent.ExecutionException: java.lang.InterruptedException: Interrupted while snapshotting table interactdbData4BI.dbo.Activities
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?]
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?]
	at io.debezium.relational.RelationalSnapshotChangeEventSource.createDataEvents(RelationalSnapshotChangeEventSource.java:534) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.relational.RelationalSnapshotChangeEventSource.doExecute(RelationalSnapshotChangeEventSource.java:179) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:96) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:297) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:281) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.connector.sqlserver.SqlServerChangeEventSourceCoordinator.executeChangeEventSources(SqlServerChangeEventSourceCoordinator.java:84) ~[debezium-connector-sqlserver-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:143) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
	at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
Caused by: java.lang.InterruptedException: Interrupted while snapshotting table interactdbData4BI.dbo.Activities
	at io.debezium.relational.RelationalSnapshotChangeEventSource.doCreateDataEventsForTable(RelationalSnapshotChangeEventSource.java:629) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at io.debezium.relational.RelationalSnapshotChangeEventSource.lambda$createDataEventsForTableCallable$6(RelationalSnapshotChangeEventSource.java:586) ~[debezium-core-3.0.7.Final.jar:3.0.7.Final]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
	... 5 more

Stack Trace: java.util.concurrent.ExecutionException: java.lang.InterruptedException: Interrupted while snapshotting table interactdbData4BI.dbo.Activities
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.createDataEvents(RelationalSnapshotChangeEventSource.java:534)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.doExecute(RelationalSnapshotChangeEventSource.java:179)
	at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:96)
	at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:297)
	at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:281)
	at io.debezium.connector.sqlserver.SqlServerChangeEventSourceCoordinator.executeChangeEventSources(SqlServerChangeEventSourceCoordinator.java:84)
	at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:143)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.InterruptedException: Interrupted while snapshotting table interactdbData4BI.dbo.Activities
	at io.debezium.relational.RelationalSnapshotChangeEventSource.doCreateDataEventsForTable(RelationalSnapshotChangeEventSource.java:629)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.lambda$createDataEventsForTableCallable$6(RelationalSnapshotChangeEventSource.java:586)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
... 5 more
k
The knowledge sources do not contain specific information about this exact error (
InterruptedException: Interrupted while snapshotting table
), so I'll share what I can based on the available context. MSSQL Source: InterruptedException During Snapshot The error you're seeing is:
Copy code
java.lang.InterruptedException: Interrupted while snapshotting table interactdbData4BI.dbo.Activities
This means the Debezium snapshot thread was interrupted mid-snapshot of the 
Activities
table. This is different from a connector configuration error — it indicates the snapshotting process was externally interrupted (e.g., a sync timeout, resource constraint, or the connector being stopped/restarted while the snapshot was in progress). Likely Causes 1. Sync timeout — The snapshot of the 
Activities
table is taking too long, and the sync job is being killed before it completes. This is common with large tables. 2. Connector restart / pod eviction — If running on Kubernetes, the connector pod may have been evicted or restarted mid-snapshot. 3. Initial wait time too short — The connector's initial waiting timeout may be expiring before the snapshot finishes. Suggested Steps 1. Check table size — If 
dbo.Activities
is a very large table, the snapshot may simply be timing out. Consider whether you need to snapshot the full table or can use a cursor-based approach. 2. Check connector version — The stack trace shows 
debezium-core-3.0.7.Final
, which corresponds to an older source-mssql connector version. The knowledge sources reference issues in versions 4.3.x. [MSSQL CDC Issue] 3. Check 
database.dbname
vs 
database.names
 — A contributor on a related MSSQL issue noted that if 
database.dbname
and 
database.names
have different values in the connector config, it can cause CDC/snapshot failures. Verify these match in your source configuration. [MSSQL CDC Issue] 4. Increase the Initial Waiting Timeout — In the source connector settings, increase the "Initial Waiting Timeout" to give the snapshot more time to complete. 5. Reset and retry — If the snapshot was partially completed and the state is now inconsistent, try resetting the connection data and re-running. 6. Check platform logs — Look at the broader Airbyte platform/worker logs around the same timestamp to see if there was a timeout, OOM kill, or pod restart that triggered the interruption. The knowledge sources don't contain a definitive fix for this specific error, so I'd recommend opening a GitHub issue at airbytehq/airbyte with your connector version, table size, and full logs if the above steps don't resolve it. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
10 Views
Open in Slack
PreviousNext
Powered by