Try turning on verbose GC logging and look if it's GC. In my experience
that's often the cause. "client application suddenly loses
its Zookeeper session" - might be client GC, or it could be server GC. See
if either of those shed light.
Patrick
On Sat, Apr 6, 2019 at 1:10 PM Norbert Kalmar
Hi Gelbana,
max_latency tells you the time elapsed between creating the request and
FinalRequestProcessor processing it. So the cause for being that high could
be basically anything.
Turning on debug log for ZooKeeper server could help pinpoint at what point
the request get stuck for so long.
Another couple of things I found:
*A couple of Zookeeper client threads are stuck at these stacktraces for
~30 seconds*
"pool-2-thread-1-EventThread" #1218 daemon prio=5 os_prio=0
tid=0x7ff3f5e23800 nid=0x5cd8 waiting on condition [0x7ff3ef803000]
java.lang.Thread.State: WAITING
I'm trying to debug a problem where our client application suddenly loses
its Zookeeper session. I concluded that by looking at the Zookeeper server
logs.
I increased the logging details for the client and found the following log
messages
> DEBUG: [07:33:33] [demo | HA | Manager] Got ping
