curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CURATOR-14) Memory leak in Curator watches
Date Mon, 08 Apr 2013 23:46:15 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jordan Zimmerman updated CURATOR-14:
------------------------------------

    Issue Type: New Feature  (was: Bug)

The only way to "fix" this is to support a Watcher pool of some kind. It wouldn't be hard
to add. Just a lot of search/replace work. 

Off the top of my head - I already have the beginnings of a Watcher cache in the private class
NamespaceWatcherMap. This could be extended so that it's exposed via the CuratorFramework
instance. Recipes would use the new cache API to allocate watchers instead of manually allocating
them.

hint - hint - whomever implements this would make a very good candidate to be a Curator committer.
                
> Memory leak in Curator watches
> ------------------------------
>
>                 Key: CURATOR-14
>                 URL: https://issues.apache.org/jira/browse/CURATOR-14
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Recipes
>            Reporter: Brandon Beck
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>         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

Mime
View raw message