Re: [I] [CURATOR-14] Memory leak in Curator watches [curator]

[via GitHub]

jira-importer commented on issue #535:
URL: https://github.com/apache/curator/issues/535#issuecomment-2604692379

   <i><a 
href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=iocanel";>iocanel</a>:</i>
   <p>This is the 3rd draft and hopefully final<img class="emoticon" 
src="https://issues.apache.org/jira/images/icons/emoticons/help_16.png"; 
height="16" width="16" align="absmiddle" alt="" border="0"/> version of the 
patch.</p>
   
   <p>The patch adds a WatcherPool for pooling NamespaceWatchers. The 
NamespaceWatcherMap is being backed by the WatcherPool: It pulls 
NamespaceWatcher instances from the pool when creates new mappings.</p>
   
   <p>Upon removal of a mapping the NamespaceWatcher (if not garbage collected 
is returned to the pool).</p>
   
   <p>Recipes allocate NamespaceWatchers from the map and remove them from the 
map when no longer needed.</p>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@curator.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org