linux怎么查看本机内存大小
601
2022-11-01
Kafka学习笔记之kafka常见报错及解决方法（topic类、生产消费类、启动类）
Kafka学习笔记之kafka常见报错及解决方法（topic类、生产消费类、启动类）
Kafka报错
0x01 启动报错
1.1 第一种错误
2017-02-17 17:25:29,224] FATAL Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)kafka.common.KafkaException: Failed to acquire lock on file .lock in /var/log/kafka-logs. A Kafka instance in another process or thread is using this directory.at kafka.log.LogManager$$anonfun$lockLogDirs$1.apply(LogManager.scala:100)at kafka.log.LogManager$$anonfun$lockLogDirs$1.apply(LogManager.scala:97)at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33)at scala.collection.mutable.WrappedArray.foreach(WrappedArray.scala:35)at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)at scala.collection.AbstractTraversable.map(Traversable.scala:104)at kafka.log.LogManager.lockLogDirs(LogManager.scala:97)at kafka.log.LogManager.
解决方法：Failed to acquire lock on file .lock in /var/log/kafka-logs.--问题原因是有其他的进程在使用kafka，ps -ef|grep kafka，杀掉使用该目录的进程即可；
1.2 第二种错误：对index文件无权限
把文件的权限更改为正确的用户名和用户组即可；目录/var/log/kafka-logs/，其中__consumer_offsets-29是偏移量；
1.3 第三种生产消费报错:jaas连接有问题
kafka_client_jaas.conf文件配置有问题16环境上/opt/dataload/filesource_wangjuan/conf下kafka_client_jaas.conf
KafkaClient {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=truekeyTab="/home/client/keytabs/client.keytab"serviceName="kafka"principal="client/dcp@DCP.COM";};
0x02 生产者报错
2.1 第一种：生产者向topic发送消息失败
[2017-03-09 09:16:00,982] [ERROR] [startJob_Worker-10] [DCPKafkaProducer.java line:62] produceR向topicdf02211发送信息出现异常org.apache.kafka.common.KafkaException: Failed to construct kafka producerat org.apache.kafka.clients.producer.KafkaProducer.
原因是配置文件：kafka_client_jaas.conf中配置有问题，keyTab的路径不对，导致的；
2.2 第二种：生产消费报错： Failed to construct kafka producer
报错关键信息：Failed to construct kafka producer
解决方法：配置文件问题：KafkaClient中serviceName应该是kafka，之前配置成了zookeeper；重启后，就好了；
配置文件如下：
KafkaServer {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=trueuseTicketCache=falseserviceName=kafkakeyTab="/etc/security/keytabs/kafka.service.keytab"principal="kafka/dcp16@DCP.COM";};KafkaClient {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=trueserviceName=kafkakeyTab="/etc/security/keytabs/kafka.service.keytab"principal="kafka/dcp16@DCP.COM";};Client {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=trueuseTicketCache=falseserviceName=zookeeperkeyTab="/etc/security/keytabs/kafka.service.keytab"principal="kafka/dcp16@DCP.COM";};
问题描述：
[kafka@DCP16 bin]$ ./kafka-console-producer --broker-list DCP16:9092 --topic topicin050511 --producer.config ../etc/kafka/producer.propertiesorg.apache.kafka.common.KafkaException: Failed to construct kafka producerat org.apache.kafka.clients.producer.KafkaProducer.
2.3 消费时报错: ERROR Unknown error when running consumer: (kafka.tools.ConsoleConsumer$)
[root@DCP16 bin]# ./kafka-console-consumer --zookeeper dcp18:2181,dcp16:2181,dcp19:2181/kafkakerberos --from-beginning --topic topicout050511 --new-consumer --consumer.config ../etc/kafka/consumer.properties --bootstrap-server DCP16:9092[2017-05-07 22:24:37,479] ERROR Unknown error when running consumer: (kafka.tools.ConsoleConsumer$)org.apache.kafka.common.KafkaException: Failed to construct kafka consumerat org.apache.kafka.clients.consumer.KafkaConsumer.
衍生问题:
kafka生产消息就会报错：
[2017-05-07 23:17:16,240] ERROR Error when sending message to topic topicin050511 with key: null, value: 0 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.
把KafkaClient更改为如下的配置，就可以 了：
KafkaClient {com.sun.security.auth.module.Krb5LoginModule requireduseTicketCache=true;};
0x03消费者报错
3.1 第一种错误：replication factor: 1 larger than available brokers: 0
消费时报错：Error while executing topic command : replication factor: 1 larger than available brokers: 0
解决办法：/confluent-3.0.0/bin 下重启daemon
./kafka-server-stop -daemon ../etc/kafka/server.properties./kafka-server-start -daemon ../etc/kafka/server.properties
然后zk重启;sh zkCli.sh -server ai186;
/usr/hdp/2.4.2.0-258/zookeeper/bin/zkCli.sh --脚本的目录
如果还报错，可以查看配置文件中下面的配置：
zookeeper.connect=dcp18:2181/kafkakerberos； --是group名称
3.2 第二种错误：TOPIC_AUTHORIZATION_FAILED
./bin/kafka-console-consumer --zookeeper DCP185:2181,DCP186:2181,DCP187:2181/kafka --from-beginning --topic wangjuan_topic1 --new-consumer --consumer.config ./etc/kafka/consumer.properties --bootstrap-server DCP187:9092[2017-03-02 13:44:38,398] WARN The configuration zookeeper.connection.timeout.ms = 6000 was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig)[2017-03-02 13:44:38,575] WARN Error while fetching metadata with correlation id 1 : {wangjuan_topic1=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient)[2017-03-02 13:44:38,677] WARN Error while fetching metadata with correlation id 2 : {wangjuan_topic1=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient)[2017-03-02 13:44:38,780] WARN Error while fetching metadata with correlation id 3 : {wangjuan_topic1=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient)
解决方法：配置文件中下面的参数中的User的U必须是大写；
super.users=User:kafka
或者有可能是server.properties中的adver.listen的IP是不对的，有可能是代码中写死的IP；
3.3 第三种错误的可能的解决方法：
无法消费，则查看kafka的启动日志中的报错信息：日志文件的所属组不对，应该是hadoop；
或者，查看kafka对应的zookeeper的配置后缀，是否已经更改，如果更改了，则topic需要重新生成才行；
3.4 第四种错误：消费的tomcat报错
[2017-04-01 06:37:21,823] [INFO] [Thread-5] [AbstractCoordinator.java line:542] Marking the coordinator DCP187:9092 (id: 2147483647 rack: null) dead for group test-consumer-group[2017-04-01 06:37:21,825] [WARN] [Thread-5] [ConsumerCoordinator.java line:476] Auto offset commit failed for group test-consumer-group: Commit offsets failed with retriable exception. You should retry committing offsets.
更改代码中，tomcat的心跳超时时间如下：
没有改之前的:;
./webapps/web/WEB-INF/classes/com/ai/bdx/dcp/hadoop/service/impl/DCPKafkaConsumer.class;
重启后，日志中显示：
[2017-04-01 10:14:56,167] [INFO] [Thread-5] [AbstractCoordinator.java line:542] Marking the coordinator DCP187:9092 (id: 2147483647 rack: null) dead for group test-consumer-group[2017-04-01 10:14:56,286] [INFO] [Thread-5] [AbstractCoordinator.java line:505] Discovered coordinator DCP187:9092 (id: 2147483647 rack: null) for group test-consumer-group.
0x04 创建topic时错误
创建topic时报错：
[2017-04-10 10:32:23,776] WARN SASL configuration failed: javax.security.auth.login.LoginException: Checksum failed Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn)Exception in thread "main" org.I0Itec.zkclient.exception.ZkAuthFailedException: Authentication failureat org.I0Itec.zkclient.ZkClient.waitForKeeperState(ZkClient.java:946)at org.I0Itec.zkclient.ZkClient.waitUntilConnected(ZkClient.java:923)at org.I0Itec.zkclient.ZkClient.connect(ZkClient.java:1230)at org.I0Itec.zkclient.ZkClient.
问题定位：是jaas文件有问题：
解决方法：server.properties文件中的super.user要和jaas文件中的keytab的principle一致；
server.properties:super.users=User:client
kafka_server_jaas.conf文件改为：
KafkaServer {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=trueuseTicketCache=falseserviceName=kafkakeyTab="/data/data1/confluent-3.0.0/kafka.keytab"principal="kafka@DCP.COM";}; KafkaClient {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=truekeyTab="/home/client/client.keytab"principal="client/DCP187@DCP.COM";}; Client {com.sun.security.auth.module.Krb5LoginModule requireduseKeyTab=truestoreKey=trueuseTicketCache=falseserviceName=zookeeperkeyTab="/home/client/client.keytab"principal="client/DCP187@DCP.COM";};
版权声明：本文内容由网络用户投稿，版权归原作者所有，本站不拥有其著作权，亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容，请联系我们jiasou666@gmail.com 处理，核实后本网站将在24小时内删除侵权内容。
相关文章
发表评论
暂时没有评论，来抢沙发吧~