y, August 28, 2013 4:25 PM
> To: users@kafka.apache.org
> Subject: Re: zookeeper session time out
>
> Ah, you maybe hitting the GC due to IO issue. You can confirm if this is
> really the case by looking at the gc.log on the broker and check if you see
> a GC entry with a small user and sys t
bject: Re: zookeeper session time out
Ah, you maybe hitting the GC due to IO issue. You can confirm if this is really
the case by looking at the gc.log on the broker and check if you see a GC entry
with a small user and sys time but high real time. We saw a similar
IO-causing-GC pauses problem
Ah, you maybe hitting the GC due to IO issue. You can confirm if this is
really the case by looking at the gc.log on the broker and check if you see
a GC entry with a small user and sys time but high real time. We saw a
similar IO-causing-GC pauses problem when compressing our request log4j
files w
Hi team,
We notice when the incoming throughput is very high, the broker has to delete
old log files to free up disk space. That caused some kind of blocking
(latency) and
frequently the broker's zookeeper session times out. Currently our zookeeper
time out threshold is 4s. We can increase it. Bu
