It's not exactly clear to me why you see NoBrokersForPartitionException
after the broker is restarted. I was thinking that one potential issue
could be that a ZK bug caused a missing watcher.
Thanks,
Jun
On Tue, Jan 7, 2014 at 9:17 PM, Cheolwoo Choi wrote:
> You mean ...
>
> ZK 3.3.4 is more
You mean ...
ZK 3.3.4 is more stable as you have been using that without problem.
Even using zk 3.3.4, it can't avoid the "NoBrokersForPartitionException" at
Producer.
It's good for me to change to zk 3.3.4,
and if I want to avoid the NoBrokersForPartitionException,
I should catch the exception,
The issues that you saw could be related to ZK. Not sure how stable 3.4.5
is. We have been using 3.3.4 and it seems stable.
Thanks,
Jun
On Tue, Jan 7, 2014 at 4:09 PM, Cheolwoo Choi wrote:
> I'm using zk-3.4.5
>
> Thanks,
>
>
>
> On Wed, Jan 8, 2014 at 1:30 AM, Jun Rao wrote:
>
> > What vers
I'm using zk-3.4.5
Thanks,
On Wed, Jan 8, 2014 at 1:30 AM, Jun Rao wrote:
> What version of ZK are you using?
>
> Thanks,
>
> Jun
>
>
> On Mon, Jan 6, 2014 at 11:30 PM, Cheolwoo Choi wrote:
>
> > Hi, all ~
> >
> > There are 3 zookepers and one broker, Kafka 0.7.2.
> > I got some temporary pr
What version of ZK are you using?
Thanks,
Jun
On Mon, Jan 6, 2014 at 11:30 PM, Cheolwoo Choi 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
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 t
