lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Des Lownds (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3953) Using many dynamic fields in filters, sorts causes OOM
Date Wed, 04 Apr 2012 21:21:24 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message