Configuring snapshot.mode for MySQL source with purged gtids issue

Summary

Debezium is unable to process the binlog due to purged gtids in MySQL source. The user needs help configuring snapshot.mode to address this issue.


Question

How can I configure snapshot.mode for mysql source. I’m having a problem where debezium cannot process the binlog because some of the gtids have been purged.

2024-02-16 14:21:54 source > java.lang.RuntimeException: java.lang.RuntimeException: io.debezium.DebeziumException: The connector is trying to read binlog starting at SourceInfo [currentGtid=null, currentBinlogFilename=mysql-bin.000001, currentBinlogPosition=1136912, currentRowNumber=0, serverId=0, sourceTime=null, threadId=-1, currentQuery=null, tableIds=[], databaseName=null], but this is no longer available on the server. Reconfigure the connector to use a snapshot when needed.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["configure", "snapshot-mode", "mysql-source", "purged-gtids", "debezium", "binlog"]