-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Bug report
What Debezium connector do you use and what version?
- Connector: PostgreSQL
- Debezium Server Version: 3.1
What is the connector configuration?
debezium.sink.type=pulsar debezium.sink.pulsar.tenant=public debezium.sink.pulsar.namespace=default debezium.sink.pulsar.client.serviceUrl=pulsar://pulsar:6650 debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector debezium.source.offset.storage.file.filename=/tmp/offsets.dat debezium.source.offset.flush.interval.ms=3999 debezium.connector.postgres=stdout debezium.source.snapshot.mode=initial debezium.source.database.hostname=postgres debezium.source.database.port=5432 debezium.source.database.user=postgres debezium.source.database.dbname=test_db debezium.source.database.server.name=postgres debezium.source.schema.include.list=public debezium.source.table.include.list=public.outbox debezium.source.plugin.name=pgoutput debezium.source.slot.name=cdc debezium.source.heartbeat.action.query=SELECT now() debezium.source.heartbeat.interval.ms=10000 debezium.source.topic.prefix=test debezium.transforms=outbox debezium.transforms.outbox.type=io.debezium.transforms.outbox.EventRouter debezium.source.database.password=secret
What is the captured database version and mode of deployment?
- PostgreSQL Version: 17.4
- Apache Pulsar Version: 3.0.8
- Deployment Mode: Docker
What behavior do you expect?
After recovering from a Pulsar timeout (>30s), Debezium Server should:
- Reconnect to PostgreSQL automatically.
- Resume processing events from the Outbox table.
or:
- Terminate the container.
What behavior do you see?
After Pulsar timeout:
- Debezium disconnects gracefully from PostgreSQL.
- If Pulsar connection is available again, new Pulsar producers are created, but Debezium keeps disconnected from PostgreSQL.
- The container remains running but stops processing events indefinitely.
Do you see the same behaviour using the latest released Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
How to reproduce the issue using our tutorial deployment?
Described on this repository
