[ 
https://issues.apache.org/jira/browse/LUCENE-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582205#comment-15582205
 ] 

Alexandre Rafalovitch commented on LUCENE-3953:
-----------------------------------------------

This looks like a very old issue with the underlying code/implementation 
changed/hardened several times.

Is this reproducible/relevant to the latest Lucene?

> Using many fields in filters, sorts causes OOM
> ----------------------------------------------
>
>                 Key: LUCENE-3953
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3953
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 4.0-ALPHA
>            Reporter: Des Lownds
>         Attachments: FieldCacheLimitPatch.patch
>
>
> I have an index with ~1M documents, and many uniquely named fields. Each 
> document only has a few fields populated, but there is a large set of dynamic 
> fields across all docs. In other words, theres many sparse fields.
> Eventually the jvm will fall over due to OOM errors, because lucene's 
> fieldCache grows without bounds. Adding more heap does not help.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to