Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
False
-
Undefined
-
Description
The error handling regarding lost CDC data in SQL Server connector is different (absent) compared to handling of similar errors in say MySQL connector.
If a connector is down, and the CDC data after the connector's committed offset is gone, it's technically a data loss which the connector should report. For example, if the expected binlog file is unavailable, the MySQL connector will fail with the following error:
io.debezium.DebeziumException: The connector is trying to read binlog starting at SourceInfo [currentGtid=null, currentBinlogFilename=mysql-bin-changelog.000744, currentBinlogPosition=83695421, 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.
The above is not true for the SQL Server connector. It will silently proceed from the earliest available LSN.