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

Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: None
    • Labels:
      None

      Description

      The trunk version of AK currently tries to incorrectly read the property (errors.deadletterqueue.topic.name) when starting a sink connector. This fails no matter what the contents of the connector config are. The ConnectorConfig does not define this property, and any calls to getString will throw a ConfigException (since only known properties are retained by AbstractConfig). 

      org.apache.kafka.common.config.ConfigException: Unknown configuration 'errors.deadletterqueue.topic.name'
          at org.apache.kafka.common.config.AbstractConfig.get(AbstractConfig.java:91)
          at org.apache.kafka.connect.runtime.ConnectorConfig$EnrichedConnectorConfig.get(ConnectorConfig.java:117)
          at org.apache.kafka.connect.runtime.ConnectorConfig.get(ConnectorConfig.java:162)
          at org.apache.kafka.common.config.AbstractConfig.getString(AbstractConfig.java:126)
          at org.apache.kafka.connect.runtime.Worker.sinkTaskReporters(Worker.java:531)
          at org.apache.kafka.connect.runtime.Worker.buildWorkerTask(Worker.java:508)
          at org.apache.kafka.connect.runtime.Worker.startTask(Worker.java:451)
          at org.apache.kafka.connect.runtime.distributed.DistributedHerder.startTask(DistributedHerder.java:873)
          at org.apache.kafka.connect.runtime.distributed.DistributedHerder.access$1600(DistributedHerder.java:111)
          at org.apache.kafka.connect.runtime.distributed.DistributedHerder$13.call(DistributedHerder.java:888)
          at org.apache.kafka.connect.runtime.distributed.DistributedHerder$13.call(DistributedHerder.java:884)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:745)
      

      This is related to the changes introduced in the KIP-298 Error Handling feature.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wicknicks Arjun Satish
                Reporter:
                wicknicks Arjun Satish
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: