Jun and Ahmed,
I am using Kafka 0.8.1.1. and Zookeeper 3.3.6. and I am hitting
exactly the same error occasionally. What is the final solution
worked for you? Thanks.
Tian
zookeeper.session.timeout.ms in consumer config.
Thanks,
Jun
On Thu, Jan 23, 2014 at 11:24 AM, Ahmed H. wrote:
> When you say "use a larger session timeout", which session timeout do you
> refer to? Is it the zookeeper session timeout variable that we define when
> creating a Kafka consumer? O
When you say "use a larger session timeout", which session timeout do you
refer to? Is it the zookeeper session timeout variable that we define when
creating a Kafka consumer? Or is there a different session timeout?
As for downgrading, that is currently not an option for the time being, so
I will
You can find some of the GC settings in
https://cwiki.apache.org/confluence/display/KAFKA/Operations
There were some ZK bugs exposed during session expiration, which were fixed
in 3.3.4. Not sure if 3.4.5 exposes any new issues. The easiest thing is
probably to avoid GC-induced ZK session timeout
Hello,
I looked at that, not sure if it is applicable or not at this point. We
used to have frequent rebalances, but that issue was mitigated by
increasing the zktimeout on the consumer side. With that said, it may still
be a problem. I have't collected any metrics concerning rebalances in a
while
Not sure how stable ZK 3.4.5 is. Could you try 3.3.4? Also, see if
https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whyaretheremanyrebalancesinmyconsumerlog?
is applicable.
Thanks,
Jun
On Wed, Jan 22, 2014 at 6:24 AM, Ahmed H. wrote:
> I have a basic Zookeeper/Kafka setup. I am still
I have a basic Zookeeper/Kafka setup. I am still on Kafka 0.8 beta 1, and
Zookeeper 3.4.5. The activity on this machine isn't massive...I would say
the Kafka queues get a consistent 1 message every 2-3 seconds, as well as
occasional spikes, but still nothing large enough to push the limits. Both
Ka
