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

Mongo Connector : No existing offset found, starting initial sync after kafka broker outage.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 0.7.5
    • mongodb-connector
    • None
    • kafka version : 1.1.0
      debezium version : 0.7.5

      kafka cluster with 3 nodes, replication factor = 3, min.insync.replicas = 2 on all topics.

    • Hide

      can not reproduce, happened twice on our cluster.

      Show
      can not reproduce, happened twice on our cluster.

      We have had debezium starting an initial sync on a kafka broker outage. This has happened to us twice so far.

      We modified debezium to disable the initial sync by replacing the return statement in the isInitialSyncExpected method in the Replicator class with "return false" (line 238). However, we don't expect that to be the cause of this issue, as this has worked fine for us in the past.

      Included in attachment are the logs for kafka connect. Duplicate lines were removed, and ips, hostnames, usernames and passwords were removed.

              Unassigned Unassigned
              jbrouwers_jira Jan Brouwers (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: