-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
None
-
False
Bug report
What Debezium connector do you use and what version?
Debezium 2.5.1.Final (Postgres connector
What is the connector configuration?
offset.storage=org.apache.kafka.connect.storage.FileOffsetBackingStore offset.storage.file.filename=/debezium_engine_wrapper/testing_config/state.dat offset.flush.interval.ms=0 connector.class=io.debezium.connector.postgresql.PostgresConnector database.hostname=localhost database.port=5432 database.user=postgres database.password=postgres database.dbname=postgres snapshot.mode=initial schema.include.list=inventory table.include.list=inventory.customers,inventory.orders,inventory.products publication.autocreate.mode=filtered plugin.name=pgoutput snapshot.max.threads=1 signal.enabled.channels=file,source signal.data.collection=inventory.debezium_signal signal.file=/debezium_engine_wrapper/testing_config/signal-file.jsonl
What is the captured database version and mode of depoyment?
PostgreSQL 15.2, Debian, docker
What behaviour do you expect?
I restart the connector to continue from the offset. At the same time signal file is provided that already contains signals to perform adhoc snapshots. I expect the snapshots to be triggered (both INCREMENTAL or BLOCKING)
What behaviour do you see?
When triggering incremental snapshots the snapshot fails with error: Incremental snapshot is not properly configured, either sinalling data collection is not provided or connector-specific snapshotting not set
When triggering BLOCKING snapshot the signal is registered but not triggered.
NOTE: This is a timing issue. If I add these signals into the file channel some time after the connector startup, everything works fine.
More information in the related discussion .
Do you see the same behaviour using the latest relesead Debezium version?
Yes, in 2.5.1.Final
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<Your answer>
How to reproduce the issue using our tutorial deployment?
I am able to reproduce it also using debezium server against the sample Debezium postgre image. With the following config
ezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector debezium.source.offset.storage.file.filename=/debezium-server/data/offsets.dat debezium.source.offset.flush.interval.ms=0 debezium.source.database.hostname=localhost debezium.source.database.port=5432 debezium.source.database.user=postgres debezium.source.database.password=postgres debezium.source.database.dbname=postgres debezium.source.database.server.name=tutorial debezium.source.schema.whitelist=inventory debezium.source.table.include.list=inventory.customers,inventory.products debezium.source.plugin.name=pgoutput debezium.source.topic.prefix=testcdc debezium.sink.type=http debezium.sink.http.url=http://localhost:8000/log_messages debezium.sink.http.headers.Content-Type=application/json debezium.format.value=json debezium.format.key=json debezium.source.signal.enabled.channels=source,file debezium.source.signal.data.collection=inventory.debezium_signal debezium.source.signal.file=/debezium-server/conf/signal-file.jsonl quarkus.log.level=trace quarkus.log.console.json=false debezium.source.snapshot.mode=initial debezium.source.snapshot.locking.mode=none
Steps:
- Run once (init load)
- Stop the server
- Add signal into the signal-file.jsonl. Any of the following (or BLOCKING version):
- Unknown macro: {"id"}
}
- Run the server again
- The snapshot fails or is not executed.
- links to
-
RHEA-2024:129636
Red Hat build of Debezium 2.5.4 release
