[
https://issues.apache.org/jira/browse/LUCENE-7652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand closed LUCENE-7652.
--------------------------------
Resolution: Duplicate
Closing now as this is either an IndexReader leak from the application side or
a duplicate of LUCENE-7657.
> LRUQueryCache / IndexSearcher.DEFAULT_QUERY_CACHE memory leak
> -------------------------------------------------------------
>
> Key: LUCENE-7652
> URL: https://issues.apache.org/jira/browse/LUCENE-7652
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: 5.4, 5.5
> Reporter: Lae
> Priority: Critical
>
> Our {{IndexSearcher.DEFAULT_QUERY_CACHE}} is set to use 32MB of heap (the
> default), however upon inspection of our application's heap, it's retaining
> ~280MB of memory and increasing slowly.
> {{LRUQueryCache.cache.size}} was at 12,099, and
> {{LRUQueryCache.cache.modCount}} was also 12,099, meaning nothing was removed
> from {{LRUQueryCache.cache}} at all.
> The keys of {{LRUQueryCache.cache}} are instances of {{SegmentCoreReaders}},
> and I've checked many of the keys, the only reference to them is
> {{LRUQueryCache.cache}}, given {{LRUQueryCache.cache}} is an
> {{IdentityHashMap}}, that means you can't even get to them outside of the
> cache because you can't get a key that's equivalent to one of these in the
> cache.
> This affectively makes {{IndexSearcher.DEFAULT_QUERY_CACHE}} a memory black
> hole.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
