You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Bob (JIRA)" <ji...@apache.org> on 2013/03/10 07:39:13 UTC

[jira] [Comment Edited] (KAFKA-799) Infinite loop trying to start a broker

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

Bob edited comment on KAFKA-799 at 3/10/13 6:37 AM:
----------------------------------------------------

Hmm indeed, I tried this on another Mac and didn't see the same issue. On the laptop with the issue, I installed 0.7.2 first and got that working and then tried the 0.8 which failed. Could that have caused the issue? Does zookeeper keep data in the same folder regardless of kafka version? It's in /tmp/zookeeper folder, right? Should there never be a null value in this case? In Scala, Some(null) is not equal to None so it probably doesn't hurt to have the safeguard in there? 
                
      was (Author: whataboutbob):
    Hmm indeed, I tried this on another Mac and didn't see the same issue. On the laptop with the issue, I installed 0.7.2 first and got that working and the tried the 0.8 which failed. Could that have caused the issue? Does zookeeper keep data in the same folder regardless of kafka version? It's in /tmp/zookeeper folder, right? Should there never be a null value in this case? In Scala, Some(null) is not equal to None so it probably doesn't hurt to have the safeguard in there? 
                  
> Infinite loop trying to start a broker 
> ---------------------------------------
>
>                 Key: KAFKA-799
>                 URL: https://issues.apache.org/jira/browse/KAFKA-799
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 0.8
>         Environment: Mac OS X 10.7.5
>            Reporter: Bob
>            Assignee: Neha Narkhede
>            Priority: Blocker
>              Labels: patch
>
> I followed the quickstart instructions
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+0.8+Quick+Start
> It caused an infinite loop while trying to start a broker. 
> [2013-03-08 16:55:19,287] ERROR Error while electing or becoming leader on broker 1 (kafka.server.ZookeeperLeaderElector)
> kafka.common.KafkaException: Can't parse json string: null
> at kafka.utils.Json$.liftedTree1$1(Json.scala:20)
> at kafka.utils.Json$.parseFull(Json.scala:16)
> at kafka.utils.ZkUtils$$anonfun$getReplicaAssignmentForTopics$1.apply(ZkUtils.scala:484)
> at kafka.utils.ZkUtils$$anonfun$getReplicaAssignmentForTopics$1.apply(ZkUtils.scala:480)
> at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:61)
> at scala.collection.immutable.List.foreach(List.scala:45)
> at kafka.utils.ZkUtils$.getReplicaAssignmentForTopics(ZkUtils.scala:480)
> at kafka.controller.KafkaController.initializeControllerContext(KafkaController.scala:451)
> at kafka.controller.KafkaController.onControllerFailover(KafkaController.scala:225)
> at kafka.controller.KafkaController$$anonfun$1.apply$mcV$sp(KafkaController.scala:87)
> at kafka.server.ZookeeperLeaderElector.elect(ZookeeperLeaderElector.scala:53)
> at kafka.server.ZookeeperLeaderElector$LeaderChangeListener.handleDataDeleted(ZookeeperLeaderElector.scala:106)
> at org.I0Itec.zkclient.ZkClient$6.run(ZkClient.java:549)
> at org.I0Itec.zkclient.ZkEventThread.run(ZkEventThread.java:71)
> Caused by: java.lang.NullPointerException
> at scala.util.parsing.combinator.lexical.Scanners$Scanner.<init>(Scanners.scala:52)
> at scala.util.parsing.json.JSON$.parseRaw(JSON.scala:71)
> at scala.util.parsing.json.JSON$.parseFull(JSON.scala:85)
> at kafka.utils.Json$.liftedTree1$1(Json.scala:17)
> ... 13 more
> I tracked the issue to unhandled Java null string in these 2 methods in ZkUtils: getReplicaAssignmentForTopics, getPartitionAssignmentForTopics.
> I am submitting a patch with the fixes. Now quickstart works fine for me.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira