lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laxman (JIRA)" <>
Subject [jira] Commented: (SOLR-1798) Memory leak in FastLUCache
Date Sat, 27 Feb 2010 14:39:05 GMT


Laxman commented on SOLR-1798:

Thanks for quick reponse Yonik.

Following is our analysis so far which may help us in resolving the issue.

1) For every commit cache instances are getting created.[]
2) For each cache config we are maintaining a list of Statistics for aggregation.

*One more observation*
>From the Solr stats page I see all the cache stats as 0 values. Following line of code
from FastLRUCache.init looks incorrect.


Because of the above line, all the cache instances created from FastLRUCache are not maintaining
any Stats info.
If this is correct, I dont understand why are we maintaining a list of stats containing zero

Or did I miss something important here?

> Memory leak in FastLUCache
> --------------------------
>                 Key: SOLR-1798
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.4, 1.5
>            Reporter: Laxman
>             Fix For: 1.5
> Every time a commit happens two Stats instances [org.apache.solr.common.util.ConcurrentLRUCache.Stats]
are leaking.
> Following code [] 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.

View raw message