Sent: Tuesday, June 25, 2013 11:58 PM
> To: users@kafka.apache.org
> Subject: Re: 0.8 throwing exception "Failed to find leader" and high-level
> consumer fails to make progress
>
> The exception is likely due to a race condition btw the logic in ZK watcher
> and the c
ct: Re: 0.8 throwing exception "Failed to find leader" and high-level
consumer fails to make progress
The exception is likely due to a race condition btw the logic in ZK watcher
and the closing of ZK connection. It's harmless, except for the weird
exception.
Thanks,
Jun
On Tue, Jun
The exception is likely due to a race condition btw the logic in ZK watcher
and the closing of ZK connection. It's harmless, except for the weird
exception.
Thanks,
Jun
On Tue, Jun 25, 2013 at 10:07 AM, Hargett, Phil <
phil.harg...@mirror-image.com> wrote:
> Possibly.
>
> I see evidence that i
Possibly.
I see evidence that its being stopped / started every 30 seconds in same cases
(due to my code). It's entirely possible that I have a race, too, in that 2
separate pieces of code could be triggering such a stop / start.
Gives me something to track down. Thank you!!
On Jun 25, 2013,
This typically only happens when the consumerConnector is shut down. Are
you restarting the consumerConnector often?
Thanks,
Jun
On Tue, Jun 25, 2013 at 9:40 AM, Hargett, Phil <
phil.harg...@mirror-image.com> wrote:
> Seeing this exception a LOT (3-4 times per second, same log topic).
>
> I'm
Seeing this exception a LOT (3-4 times per second, same log topic).
I'm using external code to feed data to about 50 different log topics over a
cluster of 3 Kafka 0.8 brokers. There are 3 ZooKeeper instances as well, all
of this is running on EC2. My application creates a high-level consumer
