英文:
Kafka Connect "Received unknown topic or partition error in fetch for partition..." Overlogging
问题
我们的Kafka Connect服务器很快就会被connect.log填满。在日志文件中不断出现的警告是：
WARN [Consumer clientId=consumer-connect-cluster-2, groupId=connect-cluster] Received unknown topic or partition error in fetch for partition connect-statuses-2 (org.apache.kafka.clients.consumer.internals.Fetcher:1340)
可能导致此警告的原因是什么，为什么它会记录为垃圾信息？它每秒记录超过1000次，我该如何停止？另外，删除该消费者组是否安全？
英文:
Our Kafka Connect server gets filled up very quickly by connect.log. The WARN that keeps appearing in the log file is:
WARN [Consumer clientId=consumer-connect-cluster-2, groupId=connect-cluster] Received unknown topic or partition error in fetch for partition connect-statuses-2 (org.apache.kafka.clients.consumer.internals.Fetcher:1340)
What may cause this warning and why it is logging as a spam?. It is getting logged more than 1000 times in a second, how can I stop that? Also is it safe to delete that consumer group?
答案1
得分: 1
如果您描述connect-statuses主题，然后查看分区2，您将看到可用的副本和领导者。
如果没有可用的副本，也没有可用的领导者，您将看到此警告消息。
英文:
If you describe the connect-statuses topic, then look at partition 2, you'll see what replicas and leaders are available.
If no replicas are available, and no leader available, you'll see this warning message
答案2
得分: 0
重启经纪人解决了问题，目前为止。找不到背后的原因。
英文:
Restarting the brokers solved the issue, for now. Couldn't find the reason behind it.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论