Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-5175

Debezium Server stops sending events to Google Cloud Pub/Sub

XMLWordPrintable

      Bug report

      What Debezium connector do you use and what version?

      I deployed debezium/server docker image as a StatefulSet on Google Kubernetes Engine (GKE).

      I tried Debezium Server 1.9.2.Final and 2.0.0.Alpha1 — both have this bug.

      What is the connector configuration?

       

      debezium.sink.type=pubsub
debezium.sink.pubsub.project.id=fastcup-224913
debezium.source.name=fastcup
debezium.source.slot.name=debezium_fastcup debezium.source.publication.name=debezium_fastcup debezium.source.database.server.name=fastcup debezium.source.connector.class=io.debezium.connector.postgresql.PostgresConnector
debezium.source.offset.storage.file.filename=/tmp/offsets.dat debezium.source.offset.flush.interval.ms=0 debezium.source.database.hostname=1.2.3.4
debezium.source.database.port=5432
debezium.source.database.user=123
debezium.source.database.password=123
debezium.source.database.dbname=fastcup debezium.source.table.include.list=public.matches debezium.source.column.include.list=public.matches.id,public.matches.status,public.matches.has_winner,public.matches.cancellation_reason debezium.source.snapshot.mode=never
debezium.source.plugin.name=pgoutput debezium.source.publication.autocreate.mode=filtered debezium.source.value.converter.schemas.enable=false debezium.source.heartbeat.topics.prefix=debezium-heartbeat debezium.source.heartbeat.interval.ms=5000 debezium.source.heartbeat.action.query=UPDATE debezium_heartbeat SET last_heartbeat=now()
debezium.transforms: ReplaceField
debezium.transforms.ReplaceField.type: org.apache.kafka.connect.transforms.ReplaceField$Value debezium.transforms.ReplaceField.blacklist: source,transaction,ts_ms 
quarkus.log.level=TRACE

       

      What is the captured database version and mode of depoyment?

      PostgreSQL 14.3 on Google Compute Engine (virtual machine).

      What behaviour do you see?

      Debezium Server stops sending events to Google Cloud Pub/Sub after a few hours after starting.

      Do you see the same behaviour using the latest relesead Debezium version?

      I tried Debezium Server 1.9.2.Final and 2.0.0.Alpha1 — both have this bug.

      Do you have the connector logs, ideally from start till finish?

      Yes, I attached TRACE logs of the moment, when Debezium Server stopped sending events.

      downloaded-logs-20220530-101317.json

        1. downloaded-logs-20220530-101317.json
          857 kB
        2. Screenshot 2022-05-30 at 10.03.40.png
          Screenshot 2022-05-30 at 10.03.40.png
          1.34 MB
        3. Screenshot 2022-05-30 at 10.03.47.png
          Screenshot 2022-05-30 at 10.03.47.png
          274 kB
        4. Screenshot 2022-05-30 at 10.07.40.png
          Screenshot 2022-05-30 at 10.07.40.png
          1.07 MB
        5. Screenshot 2022-05-30 at 10.26.01.png
          Screenshot 2022-05-30 at 10.26.01.png
          545 kB

              rh-ee-mvitale Mario Fiore Vitale
              maxpain177 Maxim Makarov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: