-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
2.5.1.Final
-
None
-
False
-
None
-
False
-
Moderate
Bug report
What Debezium connector do you use and what version?
debezium-connector-informix-2.5.0.Final with Debezium Server
debezium.source.connector.class=io.debezium.connector.informix.InformixConnector debezium.source.database.hostname=hostname debezium.source.database.port=port debezium.source.database.user=dbuser debezium.source.database.password=dbpassword debezium.source.database.dbname=dbname debezium.source.database.encrypt=false debezium.source.topic.prefix=prefix debezium.source.offset.flush.interval.ms=1000 debezium.source.include.schema.changes=false debezium.source.tombstones.on.delete=false
What is the captured database version and mode of deployment?
Informix 14.10 (Developer Edition) running on Ubuntu 20.04 VM on GCP
What behaviour do you expect?
After connector restart following a successful snapshot, changes to database tables while the connector was not running should be detected automatically.
What behaviour do you see?
Connector does not detect changes. The log ends with these entries:
2024-01-23 11:12:25,886 INFO [io.deb.con.inf.InformixSnapshotChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) A previous offset indicating a completed snapshot has been found. Neither schema nor data will be snapshot.
2024-01-23 11:12:25,912 INFO [io.deb.pip.ChangeEventSourceCoordinator] (debezium-informixconnector-chinook-change-event-source-coordinator) Snapshot ended with SnapshotResult [status=SKIPPED, offset=InformixOffsetContext [sourceInfoSchema=Schema{io.debezium.connector.informix.Source:STRUCT}, sourceInfo=SourceInfo [serverName=chinook, timestamp=null, db=chinook, snapshot=FALSE, commitLsn=120267420364, changeLsn=120267419728, txId=-1, beginLsn=120267419672], snapshotCompleted=false]]
2024-01-23 11:12:25,920 INFO [io.deb.pip.ChangeEventSourceCoordinator] (debezium-informixconnector-chinook-change-event-source-coordinator) Connected metrics set to 'true'
2024-01-23 11:12:25,922 INFO [io.deb.pip.ChangeEventSourceCoordinator] (debezium-informixconnector-chinook-change-event-source-coordinator) Starting streaming
2024-01-23 11:12:25,937 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Set CDCEngine's LSN to '120267419672' aka LSN(28,7f3018)
2024-01-23 11:12:27,823 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Begin recover: from lastBeginLsn='120267419672' to lastCommitLsn='120267420364'
2024-01-23 11:12:27,828 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Skipping already processed record 120267419728
Restarting the connector again results in the pending change events being processed, with the log ending like this:
2024-01-23 11:15:36,671 INFO [io.deb.pip.ChangeEventSourceCoordinator] (debezium-informixconnector-chinook-change-event-source-coordinator) Starting streaming 2024-01-23 11:15:36,693 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Set CDCEngine's LSN to '120267419672' aka LSN(28,7f3018) 2024-01-23 11:15:38,575 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Begin recover: from lastBeginLsn='120267419672' to lastCommitLsn='120267420364' 2024-01-23 11:15:38,580 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Skipping already processed record 12026741972820 24-01-23 11:15:38,616 INFO [io.deb.con.inf.InformixStreamingChangeEventSource] (debezium-informixconnector-chinook-change-event-source-coordinator) Recover finished: from lastBeginLsn='120267419672' to lastCommitLsn='120267420364', current Lsn='120267469516'
The same result can be achieved by applying changes to tables while the connector is running.
Do you see the same behaviour using the latest released Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
Yes
