apache / apache/curator

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

Open
#957 2 comments 0 reactions 0 assignees View on GitHub
bug imported-jira-issue
Dominant language
Java
Stars
3.2k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

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.

---
Originally reported by zealot0630, imported from: zookeeper connection leak when session expires.


  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2025-01-21

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.