[LUCENE-3953] Using many fields in filters, sorts causes OOM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 7.0
• Component/s: core/search
• Lucene Fields: New, Patch Available
• Assignee: Unassigned
• Reporter: Des Lownds
• Created: 04/Apr/12 21:10
• Updated: 28/Aug/22 13:13
• Resolved: 17/Oct/16 13:26

Description

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.

Issue Links

• blocks: SOLR-3286 Using many dynamic fields in filters, sorts causes OOM