问题来源

同事在一次spark程序中，通过spark在kafka中的topic中写入数据发生报错，错误日志如下:

2021-01-25 19:58:11,794 INFO utils.AppInfoParser: Kafka version : 2.0.0-cdh6.1.1
2021-01-25 19:58:11,794 INFO utils.AppInfoParser: Kafka commitId : null
2021-01-25 19:58:11,984 INFO codegen.CodeGenerator: Code generated in 80.049669 ms
2021-01-25 19:58:12,020 WARN clients.NetworkClient: [Producer clientId=producer-1] Connection to node -3 could not be established. Broker may not be available.
2021-01-25 19:58:12,034 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 4 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,034 INFO clients.Metadata: Cluster ID: aKKlHlDqQtalfjbLYRW1GQ
2021-01-25 19:58:12,136 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 9 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,241 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 10 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,346 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 11 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,451 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 12 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,554 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 13 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,658 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 14 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,763 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 15 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,867 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 16 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:12,971 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 17 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,076 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 18 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,181 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 19 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,285 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 20 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,390 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 21 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,495 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 22 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,600 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 23 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,704 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 24 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,808 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 25 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:13,913 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 26 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:14,044 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 27 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:14,149 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 28 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}
2021-01-25 19:58:14,254 WARN clients.NetworkClient: [Producer clientId=producer-1] Error while fetching metadata with correlation id 29 : {tagging-api-1611575841019=INVALID_REPLICATION_FACTOR}

探索步骤:

根据日志中的信息：INVALID_REPLICATION_FACTOR 初步判断，出现了不合法的副本数。
检查kafka的配置文件发现server.properties中默认的配置是三副本配置。
检查被写入kafka的topic是否存在，发现目标topic并不存在，初步怀疑是建立topic失败
得知同事以前可以在这个kafka的集群中成功执行同样的任务，遂后开始检查kafka集群的状态。
检查出有一台的kafka的broker结点挂掉，重启失败。发现是磁盘空间被占空导致重启失败，遂清理无用日志空出空间，启动kakfa发现kafka成功执行没有失败
同事再次启动程序，这个时候已经可以成功运行了。问题解决√

总结

在水下这篇文章之前，看了下报错日志。其中日志里提到了这样的一句话:Connection to node -3 could not be established. Broker may not be available.，所以，emmmm，如果仔细一下日志的话，可以更加快速的定位到问题。所以，我再次记录一下这个文章的目的是为了警醒自己，一定要仔细看日志，仔细看日志。

Spark 连接kafka报错: Error while fetching metadata with correlation id xx [topicName=INVALID_REPLICATIO]相关推荐

Kafka : WARN Error while fetching metadata with correlation id xx : {=UNKNOWN_TOPIC_OR_PARTITION}
文章目录 1.美图 2.背景 3.验证 4.场景再现 5. 场景再现 1.美图 2.背景不知道什么原因,用kafka命令发送消息时候,一直报 bin/kafka-console-producer.s ...
【Kafka】报错：Error while fetching metadata with correlation id 1 : {topic_lcc=LEADER_NOT_AVAILABLE}
文章目录 1.美图 2.背景 3. 解决方法1 3.1 原因 3.2 问题解决 4.场景再现 5.神奇日志 6.解决 6.1 解决方法 7.kafak topic坑 8. 场景再现 1.美图 2.背景 ...
flume 对接 kafka 报错： Error while fetching metadata with correlation id 35 {=INVALID_TOPIC_EXCEPTION}
flume 对接 kafka 报错:Error while fetching metadata with correlation id 35 : {=INVALID_TOPIC_EXCEPTION} ...
flume报错WARN clients.NetworkClient: Error while fetching metadata with correlation id
项目场景: 修改linux系统时间,模拟使用flume读取日志文件,并把日志文件信息传输给kafka消费,kafka消费之后,再使用flume读取kafka消费后的日志信息, 问题描述: flume在 ...
WARN Error while fetching metadata with correlation id 5 : {testtopic=LEADER_NOT_AVAILABLE}
当生产数据的时候,报错如下:提示没有可用的kafka 主节点 root@ubuntu-130:/opt/kafka_2.11-0.11.0.2/bin# ./kafka-console-produce ...
WARN Error while fetching metadata with correlation id 1 : {first=LEADER_NOT_AVAILABLE} (org.apache.
搭建Kahka集群的时候,创建生产者是遇到的问题,大坑,所以记录下来报错: 其实就是无法识别leader,那么就是当前主机变得无法识别解决方法: 配置listeners,后面接本机的ip地址就好 ...
WARN Error while fetching metadata with correlation id 1 : {hotitems=LEADER_NOT_AVAILABLE}
进入conf/server.properties 把这行注释取消加上自己的ip地址亲测有效
Navicat远程连接服务器报错ERROR 2003 (HY000) Can‘t connect to MySQL server on ‘IP‘ (10061)
1背景 Navicat远程连接服务器报错ERROR 2003 (HY000) Can't connect to MySQL server on 'IP' (10061) 但是6月份左右的时间还是可以正 ...
Spark连接oracle报错requirement failed: Decimal precision 1 exceeds max precision 0
Spark连接oracle报错requirement failed: Decimal precision 1 exceeds max precision 0 报错显示Decimal精度问题,spark ...
解决IntelliJ IDEA报错Error: java: 错误: 不支持发行版本 XX
解决IntelliJ IDEA报错Error: java: 错误: 不支持发行版本 XX 解决方法 1 解决方法 2 解决方法 3 笔者在做代码重构的时候,以前记得运行正常的代码,如今一直报错,百 ...

Spark 连接kafka报错: Error while fetching metadata with correlation id xx [topicName=INVALID_REPLICATIO]

问题来源

探索步骤:

总结

Spark 连接kafka报错: Error while fetching metadata with correlation id xx [topicName=INVALID_REPLICATIO]相关推荐

最新文章

热门文章