Uploaded image for project: 'Kafka Connector'
  1. Kafka Connector
  2. KAFKA-141

Mongo Source Connector seeks non-existing topic

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • 1.2.0
    • Source
    • None

    Description

      A general outline of this issue has been posted on stackoverflow.
      https://stackoverflow.com/questions/62441841/topic-mapping-error-kafka-connect-mongo-source-connector

      In a nutshell, the Kafka producer that underlies the MongoDB Source Connector sometimes points to the wrong (and thus non-existing) topic. The database name - that is by definition part of the topic name - is prefixed by an inexplicable number. 

      This happens during the deployment of the Mongo Source Connector, but it also popped-up during the restart of one of our Kafka Connect nodes.

      Please find the logs (nothing is logged on DEBUG level) and our connector configuration attached.

      Note that by changing the name of the connector the bug eventually does not occur. This flaky behavior is a blocker for us to go to production.

      Attachments

        Activity

          People

            ross@mongodb.com Ross Lawley
            jeffrey.vanhelden@thewarehouse.co.nz J vH
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: