未知的配置'errors.deadletterqueue.topic.name' [英] Unknown configuration 'errors.deadletterqueue.topic.name'

查看:126
本文介绍了未知的配置'errors.deadletterqueue.topic.name'的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试为Google Cloud PubSub Service配置Sink Kafka Connect。

I am trying to configure Sink Kafka Connect for Google Cloud PubSub Service.

使用以下命令配置Kafka Connect:

Using following command to configure Kafka Connect:

curl 
-X POST 
-H 'Content-Type: application/json' 
-H 'Accept: application/json' -d '{ "name": "pubsub_test", 
"config": { "connector.class": "com.google.pubsub.kafka.sink.CloudPubSubSinkConnector", 
"tasks.max": "1", 
"topics": "kafka_test_topic",
"cps.topic": "cps_test_topic", 
"cps.project": "cps_test_project" } }' http://localhost:8083/connectors

状态中,我有以下消息:

In status, I have a following message:

{"name":"pubsub_test","connector":
{"state":"RUNNING","worker_id":"connect:8083"},
"tasks":[{"state":"FAILED","trace":"org.apache.kafka.common.config.ConfigException:
Unknown configuration 'errors.deadletterqueue.topic.name'\n\tat org.apache.kafka.common.config.AbstractConfig.get(AbstractConfig.java:91)\n\tat org.apache.kafka.connect.runtime.ConnectorConfig$EnrichedConnectorConfig.get(ConnectorConfig.java:117)\n\tat org.apache.kafka.connect.runtime.ConnectorConfig.get(ConnectorConfig.java:162)\n\tat org.apache.kafka.common.config.AbstractConfig.getString(AbstractConfig.java:126)\n\tat org.apache.kafka.connect.runtime.Worker.sinkTaskReporters(Worker.java:531)\n\tat org.apache.kafka.connect.runtime.Worker.buildWorkerTask(Worker.java:508)\n\tat org.apache.kafka.connect.runtime.Worker.startTask(Worker.java:451)\n\tat org.apache.kafka.connect.runtime.distributed.DistributedHerder.startTask(DistributedHerder.java:873)\n\tat org.apache.kafka.connect.runtime.distributed.DistributedHerder.access$1600(DistributedHerder.java:111)\n\tat org.apache.kafka.connect.runtime.distributed.DistributedHerder$13.call(DistributedHerder.java:888)\n\tat org.apache.kafka.connect.runtime.distributed.DistributedHerder$13.call(DistributedHerder.java:884)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat java.lang.Thread.run(Thread.java:748)\n","id":0,"worker_id":"connect:8083"}],"type":"sink"}


推荐答案

似乎不是特定于Cloud Pub / Sub连接器,而是 Kafka的一般问题。也许您正在运行的Kafka版本没有修复。

It looks like this is not specific to the Cloud Pub/Sub connector, but is a general issue with Kafka. Perhaps you are running a version of Kafka that does not have the fix.

这篇关于未知的配置'errors.deadletterqueue.topic.name'的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆