lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1798) Memory leak in FastLRUCache
Date Sat, 06 Mar 2010 22:46:27 GMT

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

Yonik Seeley updated SOLR-1798:
-------------------------------

    Attachment: SOLR-1798.patch

New patch that fixes the cumulative stats by adding in an entry in the list for cumulative
stats and incrementing them for every cache that is closed.

Longer term, we might want a hash set or something (if we start having per-segment caches)
but more changes will be necessary then anyway.

> Memory leak in FastLRUCache
> ---------------------------
>
>                 Key: SOLR-1798
>                 URL: https://issues.apache.org/jira/browse/SOLR-1798
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.4, 1.5
>            Reporter: Laxman
>            Assignee: Yonik Seeley
>             Fix For: 1.5
>
>         Attachments: SOLR-1798.patch, SOLR-1798.patch
>
>
> Every time a commit happens two Stats instances [org.apache.solr.common.util.ConcurrentLRUCache.Stats]
are leaking.
> Following code [org.apache.solr.search.FastLRUCache] to maintain cumulative cache statistics
causing this Stats object leak. 
> {noformat}
>     cumulativeStats = (List<ConcurrentLRUCache.Stats>) persistence;
>     cumulativeStats.add(cache.getStats());
> {noformat}
> Everytime a *commit* happens a new cache object is getting created and its stats is added
to the list which is not released at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message