Gerrit Trigger SSH often gets stuck in CLOSED WAITING about gerrit-events HOT 4 CLOSED

What is "CLOSED_WAITING"? I don't know such status name. Googling but not found.

from gerrit-events.

Maybe not CLOSED_WAITING but TIMED_WAITING, it is one of thread status that is defined by Thread.State.

I checked heapdump with jvisualvm (used below "contains" filter in classes tab)

gerrit.trigger
gerritevents
com.jcraft.jsh

• Observed a lot of RefReplicated event objects.
• ReplicationCache has a lot of RefReplicatedId instance.
• Cannot get actual thread status from heapdump because it is managed by class field in sum.misc.VM.

Maybe your system has gerrit slave then do replication. I guess your issue is caused by replication status.

If you are facing issue related to #66, #68, #69, event object is no longer generated. To identify the root cause, you need to get more heapdump.

from gerrit-events.

@rinrinne Will try to get more heap dumps. The WAITING was looking at the actual SSH status with netstat. I'll provide the exact commands my team used for that tomorrow as an update on this comment.

UPDATE:

Commands we use

netstat -an
GERRIT_SSH_PORT=29418 

netstat -an | grep ${GERRIT_SSH_PORT} 

netstat -an | grep ${GERRIT_SSH_PORT} | grep ESTABLISHED

from gerrit-events.

We are no longer seeing this specific issue of the port not being ESTABLISHED, but in a CLOSED_blah state.

from gerrit-events.