kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mickael Maison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6061) "ERROR Error while electing or becoming leader on broker 13 (kafka.server.ZookeeperLeaderElector) kafka.common.KafkaException: Can't parse json string: null" should print out information on which zookeeper path contains the null element
Date Sat, 21 Oct 2017 12:47:02 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213889#comment-16213889
] 

Mickael Maison commented on KAFKA-6061:
---------------------------------------

DUP of https://issues.apache.org/jira/browse/KAFKA-5885

> "ERROR Error while electing or becoming leader on broker 13 (kafka.server.ZookeeperLeaderElector)
 kafka.common.KafkaException: Can't parse json string: null" should print out information
on which zookeeper path contains the null element
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-6061
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6061
>             Project: Kafka
>          Issue Type: Bug
>          Components: zkclient
>    Affects Versions: 0.10.2.1
>            Reporter: Koelli Mungee
>              Labels: newbie
>             Fix For: 1.1.0
>
>
> The controller enters a loop with the error as 
> {code:java}
> [2017-10-12 21:40:09,532] ERROR Error while electing or becoming leader on broker 13
(kafka.server.ZookeeperLeaderElector) 
> kafka.common.KafkaException: Can't parse json string: null 
> at kafka.utils.Json$.liftedTree1$1(Json.scala:40) 
> at kafka.utils.Json$.parseFull(Json.scala:36) 
> at kafka.utils.ZkUtils$$anonfun$getReplicaAssignmentForTopics$1.apply(ZkUtils.scala:684)

> at kafka.utils.ZkUtils$$anonfun$getReplicaAssignmentForTopics$1.apply(ZkUtils.scala:680)

> at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59) 
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) 
> at kafka.utils.ZkUtils.getReplicaAssignmentForTopics(ZkUtils.scala:680) 
> at kafka.controller.KafkaController.initializeControllerContext(KafkaController.scala:736)

> at kafka.controller.KafkaController.onControllerFailover(KafkaController.scala:334) 
> at kafka.controller.KafkaController$$anonfun$1.apply$mcV$sp(KafkaController.scala:167)

> at kafka.server.ZookeeperLeaderElector.elect(ZookeeperLeaderElector.scala:84) 
> {code}
> A kafka-topics --describe can be issued to figure out which topic partition has the problem.
However, this would be easier for the user if the actual zk path with the null or malformed
entry would be printed out.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message