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

Debezium not recovering from connection errors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • Backlog
    • None
    • postgresql-connector
    • None
    • False
    • None
    • False
    • Critical

      Bug report

      To reproduce:

      • Run postgres db in one machine.
      • Run confluentinc/cp-kafka-connect by using docker or whatever in another machine.
      • Disconnect network between docker vs postgres database server.

      Then we will see some error messages and retry to connect message, but after the message "io.debezium.DebeziumException: Couldn't obtain encoding for database" is thrown, debezium gave up to retry the connection.

      Expectation: Debezium should retry to connect until I enable the network connection again.

      What Debezium connector do you use and what version?

      2.5.2.Final, 2.6.0.Final and 2.6.1.Final

      What is the connector configuration?

      {    "connector.class": "io.debezium.connector.postgresql.PostgresConnector",     "database.hostname": "db.myhost.com",     "database.port": "5432",     "database.user": "admin",     "database.password": "admin-password",     "database.dbname" : "postgres_test",     "slot.name" : "slotname",    "database.tcpKeepAlive": "true",    "database.server.name": "myserver",   	"key.converter.schema.registry.url" : "http://schema-registry:8081",    "value.converter.schema.registry.url" : "http://schema-registry:8081",    "key.converter" : "io.confluent.connect.avro.AvroConverter",    "value.converter" : "io.confluent.connect.avro.AvroConverter",        "plugin.name" : "pgoutput",	"table.include.list": "public.mytable""heartbeat.interval.ms" : "60000",    "errors.tolerance": "all",    "errors.deadletterqueue.topic.name": "db.source.errors",    "errors.deadletterqueue.context.headers.enable": "true",    "topic.prefix": "app"  } 

      What is the captured database version and mode of depoyment?

      on-premises, Postgres 13.3

      What behaviour do you expect?

      Debezium should retry to connect until the network connection is enabled again.

      What behaviour do you see?

      Stop retry to connect.

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

      Yes

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

      Look at attached file.

      How to reproduce the issue using our tutorial deployment?

      Reference to above.

              Unassigned Unassigned
              hapem85 Harris Nguyen (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: