John Fung created KAFKA-711:
-------------------------------

             Summary: NPE in TRUNK broker
                 Key: KAFKA-711
                 URL: https://issues.apache.org/jira/browse/KAFKA-711
             Project: Kafka
          Issue Type: Bug
            Reporter: John Fung
This issue happens in Trunk only.

** To reproduce the issue:

1. Start zookeeper:
    $ bin/zookeeper-server-start.sh config/zookeeper.properties
2. Start broker:
    $ bin/kafka-server-start.sh config/server.properties
3. Start producer:
    $ bin/kafka-run-class.sh kafka.perf.ProducerPerformance --broker-list localhost:9092 --messages 100 --topics topic_001 --batch-size 50 --threads 1 --message-size 200
** Broker exception:

[2013-01-18 10:11:41,241] ERROR Replica Manager on Broker 0: Error processing leaderAndISR request LeaderAndIsrRequest(0,5,,1000,Map((topic_001,0) -> PartitionStateInfo(LeaderIsrAndControllerEpoch({ "ISR":"0","leader":"0","leaderEpoch":"0" },1),1)),Set(id:0,host:jfung-ld.linkedin.biz,port:9092),1) (kafka.server.ReplicaManager)
java.lang.NullPointerException
    at kafka.log.OffsetIndex.entries(OffsetIndex.scala:285)
    at kafka.log.OffsetIndex$$anonfun$1.apply(OffsetIndex.scala:88)
    at kafka.log.OffsetIndex$$anonfun$1.apply(OffsetIndex.scala:88)
    at kafka.utils.Logging$class.info(Logging.scala:67)
    at kafka.log.OffsetIndex.info(OffsetIndex.scala:52)
    at kafka.log.OffsetIndex.<init>(OffsetIndex.scala:87)
    at kafka.log.LogSegment.<init>(LogSegment.scala:37)
    at kafka.log.Log.loadSegments(Log.scala:132)
    at kafka.log.Log.<init>(Log.scala:75)
    at kafka.log.LogManager.createLogIfNotExists(LogManager.scala:202)
    at kafka.log.LogManager.getOrCreateLog(LogManager.scala:179)
    at kafka.cluster.Partition.getOrCreateReplica(Partition.scala:77)
    at kafka.cluster.Partition$$anonfun$1.apply(Partition.scala:142)
    at kafka.cluster.Partition$$anonfun$1.apply(Partition.scala:142)
    at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:206)
    at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:206)
    at scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:61)
    at scala.collection.immutable.List.foreach(List.scala:45)
    at scala.collection.TraversableLike$class.map(TraversableLike.scala:206)
    at scala.collection.immutable.List.map(List.scala:45)
    at kafka.cluster.Partition.makeLeader(Partition.scala:142)
    at kafka.server.ReplicaManager.kafka$server$ReplicaManager$$makeLeader(ReplicaManager.scala:219)
    at kafka.server.ReplicaManager$$anonfun$becomeLeaderOrFollower$3.apply(ReplicaManager.scala:199)
    at kafka.server.ReplicaManager$$anonfun$becomeLeaderOrFollower$3.apply(ReplicaManager.scala:191)
    at scala.collection.immutable.Map$Map1.foreach(Map.scala:105)
    at kafka.server.ReplicaManager.becomeLeaderOrFollower(ReplicaManager.scala:191)
    at kafka.server.KafkaApis.handleLeaderAndIsrRequest(KafkaApis.scala:155)
    at kafka.server.KafkaApis.handle(KafkaApis.scala:65)
    at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:41)
    at java.lang.Thread.run(Thread.java:662)
** ProducerPerformance exception:

[2013-01-18 10:07:02,779] ERROR Error in handling batch of 50 events (kafka.producer.async.ProducerSendThread)
kafka.common.FailedToSendMessageException: Failed to send messages after 3 tries.
    at kafka.producer.async.DefaultEventHandler.handle(DefaultEventHandler.scala:87)
    at kafka.producer.async.ProducerSendThread.tryToHandle(ProducerSendThread.scala:104)
    at kafka.producer.async.ProducerSendThread$$anonfun$processEvents$3.apply(ProducerSendThread.scala:87)
    at kafka.producer.async.ProducerSendThread$$anonfun$processEvents$3.apply(ProducerSendThread.scala:67)
    at scala.collection.immutable.Stream.foreach(Stream.scala:254)
    at kafka.producer.async.ProducerSendThread.processEvents(ProducerSendThread.scala:66)
    at kafka.producer.async.ProducerSendThread.run(ProducerSendThread.scala:44)
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