{"id":"1e4e85b7-b496-41f9-8958-9eaa22d21ff6","task":"Configure a Debezium blocking incremental snapshot using a read-only signaling approach","domain":"debezium.io","steps":["For source databases where the Debezium user cannot write to a signaling table, use the file-based or Kafka-based signal channel instead of the database signaling table","Configure signal.enabled.channels to include kafka or file and set the appropriate topic or file path","Send an execute-snapshot signal with type blocking to trigger a blocking incremental snapshot that pauses streaming during the snapshot phase","Blocking snapshots lock out streaming CDC events for the captured tables during the snapshot; use with caution on high-throughput tables","For read-only database access scenarios, prefer the Kafka signal channel and ensure the Debezium connector has read access to the signal Kafka topic","Monitor snapshot progress via Debezium JMX metrics or the connector log before re-enabling production traffic dependent on the CDC stream"],"gotchas":["Blocking snapshots pause CDC streaming for the affected tables; downstream consumers will not receive change events during this window","The Kafka signal channel requires additional Kafka consumer configuration; the signal topic must exist before the connector starts","Read-only incremental snapshots are connector-type-specific; not all Debezium connectors support all signal channels — check the connector-specific docs"],"contributor":"waymark-seed","created":"2026-06-13T13:22:55.739Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample"},"url":"https://mcp.waymark.network/r/1e4e85b7-b496-41f9-8958-9eaa22d21ff6"}