[KAFKA-8121] ZooKeeperClient session expiry thread may leave clients behind after close

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0, 2.2.1
• Assignee: Rajini Sivaram
• Reporter: Rajini Sivaram
• Reviewer: Ismael Juma
• Created: 18/Mar/19 11:47
• Updated: 18/Mar/19 18:13
• Resolved: 18/Mar/19 18:13

Description

Test failure after merging KAFKA-8118:

java.lang.AssertionError: Found unexpected threads during @AfterClass, allThreads=Set(/127.0.0.1:51186 to /127.0.0.1:40791 workers Thread 3, metrics-meter-tick-thread-2, main, Signal Dispatcher, Reference Handler, zk-session-expiry-handler0-SendThread(localhost:35825), zk-session-expiry-handler0-EventThread, scala-execution-context-global-1903, Test worker, scala-execution-context-global-34, scala-execution-context-global-5352, scala-execution-context-global-234, Finalizer, scala-execution-context-global-235, /127.0.0.1:51186 to /127.0.0.1:40791 workers Thread 2, metrics-meter-tick-thread-1), unexpected=Set(zk-session-expiry-handler0-EventThread)
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at kafka.zk.ZooKeeperTestHarness$.verifyNoUnexpectedThreads(ZooKeeperTestHarness.scala:129)
	at kafka.zk.ZooKeeperTestHarness$.tearDownClass(ZooKeeperTestHarness.scala:114)
	at kafka.zk.ZooKeeperTestHarness.tearDownClass(ZooKeeperTestHarness.scala)

Issue Links

• links to: GitHub Pull Request #6462