[ZOOKEEPER-2407] EventThread in ClientCnxn can't be closed when SendThread exits because of auth failed during reconnection

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5.1
• Assignee: sunhaitao
• Reporter: sunhaitao
• Created: 30/Mar/16 11:21
• Updated: 03/Feb/22 08:50

Description

EventThread in ClientCnxn can't be closed when SendThread exits because of auth failed during reconnection.
for send thread if it is in authfailed state, the send thread exits,but the event thread is still running.

observation:
use jstack tho check the thread running they find the send thread no longer exists but event thread is still threre
even when we call zookeeper.close(),the eventthread is still there.

Stack trace:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:514)

Issue Links

• is duplicated by: ZOOKEEPER-3059 EventThread leak in case of Sasl AuthFailed