kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Stein <joe.st...@stealth.ly>
Subject Re: kafka.common.NoBrokersForPartitionException: Partition = null
Date Tue, 07 Jan 2014 07:46:53 GMT
That issue has been uncovered
https://issues.apache.org/jira/browse/KAFKA-778 as occurring when the
producer sees 0 partitions for a topic.

A quick fix might be to change over your topic name to something new so it
gets auto created again and disband the old topic name.

Longer term fix would be to move on to 0.8.0

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/


On Tue, Jan 7, 2014 at 2:30 AM, Cheolwoo Choi <prorhap@gmail.com> wrote:

> Hi, all ~
>
> There are 3 zookepers and one broker, Kafka 0.7.2.
> I got some temporary problems in zk cluster enviornment, but, any zk
> processes didn't go down.
>
> A broker got zk session timeout message, then got zk disconnected and
> expired message.
> After 10 secs, the broker reconnected to the zk with new zk session id,
> then it regitsterd all topics successfully.
>
> But, kafka producers continuously throw
> "kafka.common.NoBrokersForPartitionException: Partition = null".
> The broker had got back in stable. However, producers didn't stop to throw
> the exceptions.
>
> How can I prevent that problem ?
>
> Thanks,
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message