[
https://issues.apache.org/jira/browse/CURATOR-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625983#comment-13625983
]
Jordan Zimmerman commented on CURATOR-14:
-----------------------------------------
This will be difficult to fix unless Curator adds some support for pooled
watches. AFAIK, there's no way to clear a watch in ZooKeeper. So, it could be
argued, that this is a client problem. You could get the same results by using
ZooKeeper directly. i.e. Add new watches in a loop.
> Memory leak in Curator watches
> ------------------------------
>
> Key: CURATOR-14
> URL: https://issues.apache.org/jira/browse/CURATOR-14
> Project: Apache Curator
> Issue Type: Bug
> Reporter: Brandon Beck
> Assignee: Jordan Zimmerman
> Attachments: MemoryTest.java
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
