This problem is so mysterious to me that I am hesitant to make any definitive
statements regarding the scope of the issue. In the staging environment where
the problem was originally seen the GC logs were not enabled. In that
environment the session timeouts persisted for a long time (and ope
James.
Thanks for reporting this. So the issue only shows up at Kafka startup
time? After that, the GC time is back to normal again?
Jun
On Tue, Apr 28, 2015 at 1:48 PM, James Lent wrote:
> I have filed a bug report with Oracle on this issue today. I have not yet
> been assigned a bug number.
The JDK bug report I submitted on this issue has been accepted and it is under
review:
https://bugs.openjdk.java.net/browse/JDK-8079274
Here is what the ParNewGC pauses look like in the Kafka logs in one of our
environments (earlier I provided logs from the test program).
In this case I had al
Here is what the ParNewGC pauses look like in the Kafka logs in one of our
environments (earlier I provided logs from the test program).
In this case I had already increased the ZooKeeper session timeout to 20
seconds so that it did not trigger a communication failure while waiting for GC
to fi
I have filed a bug report with Oracle on this issue today. I have not yet been
assigned a bug number. I thought the issue might be of general interest to the
Kafka community and I have a suggestion for a configuration change that works
around the issue in case other people tun into it.
First
