[
https://issues.apache.org/jira/browse/LUCENE-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Des Lownds updated LUCENE-3953:
-------------------------------
Summary: Using many fields in filters, sorts causes OOM (was: Using many
dynamic fields in filters, sorts causes OOM)
> Using many fields in filters, sorts causes OOM
> ----------------------------------------------
>
> Key: LUCENE-3953
> URL: https://issues.apache.org/jira/browse/LUCENE-3953
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/search
> Affects Versions: 4.0
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
