curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Commented] (CURATOR-14) Memory leak in Curator watches
Date Mon, 08 Apr 2013 23:38:16 GMT


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:
>             Project: Apache Curator
>          Issue Type: Bug
>            Reporter: Brandon Beck
>            Assignee: Jordan Zimmerman
>         Attachments:
> 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

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:

View raw message