[CURATOR-14] Memory leak in Curator watches
Open
imported-jira-issue
rfe
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
The JVM runs out of memory if you repetitively create a PathChildrenCache, start it then immediately stop it. It appears that the memory is taken up by a watch that isn't ever cleaned up. Curator attempts to do some pooling of watches, but doesn't seem to use the path in the pooling.
---
Originally reported by bbeck, imported from: Memory leak in Curator watches
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.