kafka使用时常见的几个错误汇总

菠菜很好吃

已于 2023-03-20 11:35:56 修改

阅读量7.2k

点赞数 2

分类专栏： kafka 文章标签： kafka 分布式 java

于 2022-11-26 16:23:52 首次发布

本文链接：https://blog.csdn.net/paulwang040/article/details/128033856

版权

kafka 专栏收录该内容

6 篇文章 0 订阅

订阅专栏

本文档详细记录了Kafka在启动和使用过程中遇到的三种常见错误：连接节点失败、集群ID不匹配和消费不到数据。针对这些问题，提出了相应的解决方案，包括修改配置文件、删除并重新创建topic、重启服务等。通过这些步骤，可以有效地解决Kafka在实际操作中可能遇到的问题。

摘要由CSDN通过智能技术生成

一、启动报错

WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
解决：重启kafka
org.apache.kafka.common.KafkaException: Socket server failed to bind to 114.115.20.100:9092: Cannot
解决：在kafka安装目录的conf下，编辑server.properties,添加如下内容

listeners=PLAINTEXT://:9092
advertised.listeners=PLAINTEXT://114.115.20.100:9092

二、使用报错

The Cluster ID h71epGCWSj6mfBVnsRc-fA doesn’t match stored clusterId Some(RqHGN0qGQ-iXs6idJTZ6rg) in meta.properties. The broker is trying to join the wrong cluster. Configured zookeeper.connect may be wrong.
含义：使用zookeeper集群和kafka匹配id的时候没匹配上，导致连接报错
终极解决：删除kafka-logs,删除topic重新启动zk和kafka

org.apache.kafka.common.network.InvalidReceiveException: Invalid receive (size = 1195725856 larger than 104857600)
解决：删除topic

WARN [Producer clientId=console-producer] Got error produce response with correlation id 5 on topic-partition test-2, retrying (2 attempts left). Error: NOT_LEADER_OR_FOLLOWER (org.apache.kafka.clients.producer.internals.Sender)
[2023-01-30 17:47:45,960] WARN [Producer clientId=console-producer] Received invalid metadata error in produce request on partition test-2 due to org.apache.kafka.common.errors.NotLeaderOrFollowerException: For requests intended only for the leader, this error indicates that the broker is not the current leader. For requests intended for any replica, this error indicates that the broker is not a replica of the topic partition… Going to request metadata update now (org.apache.kafka.clients.producer.internals.Sender)
解决：删除kafka-logs删除topic重新启动zk和kafka