You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Des Lownds (Commented) (JIRA)" <ji...@apache.org> on 2012/04/04 23:21:24 UTC
[jira] [Commented] (LUCENE-3953) Using many dynamic fields in
filters, sorts causes OOM
[ https://issues.apache.org/jira/browse/LUCENE-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246744#comment-13246744 ]
Des Lownds commented on LUCENE-3953:
------------------------------------
I would appreciate feedback on the attached patch, which uses a size limited LinkedHashMap for innercache if the system property "lucene.fieldCache.maxFields" is set. If the property is not set, system uses old behavior.
> Using many dynamic 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org