someone can help to analysis it？
> 在 2017年11月10日，上午11:08，Json Tu 写道：
>
> I‘m so sorry for my poor english.
>
> what I really means is my broker machine is configured as 8 core 16G. but my
> jvm configure is as below.
> java -Xmx1G -Xms1G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20
> -XX:Init
Guozhang Wang
> 主题: Re: Kafka 0.9.0.1 partitions shrink and expand frequently after restart
> the broker
>
> I‘m so sorry for my poor english.
>
> what I really means is my broker machine is configured as 8 core 16G. but my
> jvm configure is as below.
> java -Xmx
I‘m so sorry for my poor english.
what I really means is my broker machine is configured as 8 core 16G. but my
jvm configure is as below.
java -Xmx1G -Xms1G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20
-XX:InitiatingHeapOccupancyPercent=35 -XX:+DisableExplicitGC
-Djava.awt.headless=true -Xloggc
I've seen this before and it was due to long GC pauses due in large part to
a memory heap > 8 GB.
--John
On Thu, Nov 9, 2017 at 8:17 AM, Json Tu wrote:
> Hi,
> we have a kafka cluster which is made of 6 brokers, with 8 cpu and
> 16G memory on each broker’s machine, and we have about 1600 t
Yep, the team here, including Ismael, pointed me in the right direction,
which was much appreciated. :)
On Thu, Nov 9, 2017 at 10:02 AM, Viktor Somogyi
wrote:
> I'm happy that it's solved :)
>
> On Thu, Nov 9, 2017 at 3:32 PM, John Yost wrote:
>
> > Excellent points Viktor! Also, the reason I m
Excellent points Viktor! Also, the reason I mistakenly went > 8 GB memory
heap was due to OOM errors that were being thrown when I upgraded from
0.9.0.1 to 0.10.0.0 and forgot to explicitly set the message format to
0.9.0.1 because we needed to support the older clients and the
corresponding format
I'm happy that it's solved :)
On Thu, Nov 9, 2017 at 3:32 PM, John Yost wrote:
> Excellent points Viktor! Also, the reason I mistakenly went > 8 GB memory
> heap was due to OOM errors that were being thrown when I upgraded from
> 0.9.0.1 to 0.10.0.0 and forgot to explicitly set the message forma
Hi Json.
John might have a point. It is not reasonable to have more than 6-8GB of
heap provided for the JVM that's running Kafka. One of the reason is GC
time and the other is that Kafka relies heavily on the OS' disk read/write
in-memory caching.
Also there were a few synchronization bugs in 0.9
Hi,
we have a kafka cluster which is made of 6 brokers, with 8 cpu and 16G
memory on each broker’s machine, and we have about 1600 topics in the
cluster，about 1700 partitions’ leader and 1600 partitions' replica on each
broker.
when we restart a normal broke, we find that there are 500
