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

Debezium Postgres Connector fails to connect to Postgres Cluster after a failover, no changes are captured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Major Major
    • None
    • 3.0.7.Final
    • postgresql-connector
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      When a Debezium Postgres connector connected to postgres cluster using VIP whenever db switches from primary to secondary connector task fails and does not restart, we have to manually delete the connector and make a new connector .

      While recreating the connector sometimes it stuck at the process of creating the `slot` .
      In db log it is shows that the slot is active for some other PID hence slot creation process stuck and when we check the status of connector it shows running but it does not capture the changes.

              Unassigned Unassigned
              rhn-support-aboucham Abel Bouchama
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: