Yes, this is a bug in 0.7. It has been fixed in 0.8. Thanks,
Jun On Tue, Oct 2, 2012 at 1:04 AM, Milind Parikh <milindpar...@gmail.com>wrote: > My understanding is that on a Offset Request with incorrect partition (say > partition 1 when only partition 0 exists), it should through an error > through RESPONSE_HEADER. In particular, it should indicate an error code of > 3 > > WrongPartition 3 You tried to access a partition that doesn't > exist > (was not between 0 and (num_partitions - 1)). > > Instead Kafka through an internal exception at the server level and closes > the socket. > > [2012-10-02 00:55:54,136] WARN Wrong partition 1 valid partitions (0,0) > (kafka.log.LogManager) > [2012-10-02 00:55:54,136] ERROR Closing socket for /127.0.0.1 because of > error (kafka.network.Processor) > kafka.common.InvalidPartitionException: wrong partition 1 > at kafka.log.LogManager.getLogPool(LogManager.scala:163) > at kafka.log.LogManager.getLog(LogManager.scala:185) > at kafka.log.LogManager.getOffsets(LogManager.scala:176) > at > > kafka.server.KafkaRequestHandlers.handleOffsetRequest(KafkaRequestHandlers.scala:129) > at > > kafka.server.KafkaRequestHandlers$$anonfun$handlerFor$5.apply(KafkaRequestHandlers.scala:42) > at > > kafka.server.KafkaRequestHandlers$$anonfun$handlerFor$5.apply(KafkaRequestHandlers.scala:42) > at kafka.network.Processor.handle(SocketServer.scala:296) > at kafka.network.Processor.read(SocketServer.scala:319) > at kafka.network.Processor.run(SocketServer.scala:214) > at java.lang.Thread.run(Thread.java:679) > > > Is this a bug? > > Regards > Milind >
