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
Known 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
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp