[CURATOR-437] zookeeper connection leak when session expires.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0.0
• Component/s: Client
• Assignee: Unassigned
• Reporter: zealot
• Created: 19/Oct/17 12:36
• Updated: 20/Oct/17 08:45

Description

https://github.com/apache/curator/blob/master/curator-client/src/main/java/org/apache/curator/utils/InjectSessionExpiration.java#L97

Curator inject will set zookeeper state to CLOSED when session expires without close zk associated threads.

If state set to CLOSED, ZooKeeper.close() function won't be able to release resources properly, which lead to memory and connection leak.

To reproduce, create a curator client, then shutdown zk server, wait for session timeout, restart the zk server. There will be two ZooKeeper instances and two connections to the server.