[
https://issues.apache.org/jira/browse/BLUR-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron McCurry closed BLUR-370.
------------------------------
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=20ef55430cc6e81c8ef98ee0754d6c5c70aaa6b0
> Memory leak when using facets in 0.2.3
> --------------------------------------
>
> Key: BLUR-370
> URL: https://issues.apache.org/jira/browse/BLUR-370
> Project: Apache Blur
> Issue Type: Bug
> Components: Blur
> Affects Versions: 0.2.3
> Reporter: Aaron McCurry
> Assignee: Aaron McCurry
> Priority: Blocker
> Fix For: 0.2.4
>
>
> Code in a new class DeepPaging that keeps up with IndexReader generations and
> pointers to previous search positions to allow for faster paging through
> results was enabled in 0.2.3. This code used the Lucene Query objects
> themselves as keys in the lru cache. This means the FacetQuery is also
> placed into the lru cache. The FacetQuery holds a reference the
> FacetExecutor which holds references to the BitSets that are built up during
> the facet execution.
> Long story short if facets are used, up to 1000 BitSets per shard per table
> can be held on the heap and this can cause OOM errors.
> As a work around on 0.2.3 you can set blur.shard.deep.paging.cache.size=1 in
> the blur-site.properties file. Do not set it to 0, this will cause another
> issue where NO cache values are ever released.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
