The first thing I would do is update to the latest Java 8 release. Just in
case you are hitting any G1GC bugs in such an old version.
Mark
On Thu, 22 Aug 2019, 07:17 Xiaobing Bu, wrote:
> it not a network issues, since i had capture the network packets.
> when the GC remark and unloading class,
it not a network issues, since i had capture the network packets.
when the GC remark and unloading class, we guess the java application is in
stop the world mode, and can not send heartbeat to zookeeper, and after
some time, the broker is disconnected from the cluster,
so anther clients and brokers
Hi
on 2019/8/22 13:48, Xiaobing Bu wrote:
[2019-08-07 02:30:04,802] WARN Attempting to send response via channel for
which there is no open connection, connection id 10.97.133.17:9092
-10.97.200.19:58674-52592642 (kafka.network.Processor)
It seems the network issues.
Did you double check the n
Hi all,
Our kafka cluster on production environment have some problem, some brokers
connect to zookeeper timeout almost everyday. There are four brokers, each
has 10 core CPU and 8G memory.
The following is the server.log , it said broker can not connect to
zookeeper. I had capture packets using t
