lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sadaf Aslam <>
Subject RE: OOM error
Date Fri, 06 Jan 2017 19:43:17 GMT
Thanks for the suggestion Uwe.

We will look into upgrading to a newer version. But upgrading to 6 would mean using Java 8
and we are not ready for that yet.

We also want to start using DrillSideways. What version was that introduced in? I am using
version 4.4 and DrillSideways is available but it is not the version that is being used in
most examples online. What is the first stable version that would allow me to use it with
the least amount of upgrade work involved. Also, I want to use FacetFields instead of CategoryPaths.

Is there a good webpage that gives the summary of the features introduced into a version?
I looked at but couldn’t find when DrillSideways (or FacetFields)
was introduced.


From: Uwe Schindler []
Sent: December-23-16 1:27 PM
To:; Sadaf Aslam <>
Subject: Re: OOM error


For sorting you should add the fields as DocValues type in addition to indexed fields (if
you also query on them). That ist the problem. But for that you should update your Lucene

For that reason Lucene 6 no longer has FieldCache, which emulates DocValues loading everything
to heap, which is horrible for StringFields.

Am 23. Dezember 2016 18:14:50 MEZ schrieb Sadaf <<>>:


This is the index we are using:
Number of fields: 355.
Number of documents: 225 thousand.
Number of terms: 5522 thousand.
The index size is around 800MB.
TermInfos index divisor: 1
Index format: Lucene 4.0.
We are getting Java OutOfMemory error with searches. We are using a heap
size of 1GB. We are not able to increase our heap size.
Looking at the HeapDump, we have two suspects: FieldCacheImpl and
The searches we are doing have a lot of sorts. The sorting is being done on
string fields. I don’t have much experience with OutOfMemory errors or with
Lucene. What should I try to do?
- Should I try to play with the swappiness on the server. Currently set to
- We are creating a new IndexSearcher for each search? Should I just have
one? If I do that, will my results be updated as new documents are being
added to the index?
- If you think that sorting on StringFields is the problem can you give me
some pointers on what the usual suspects are?
-      Should I insist that we need more Heap?
Thanks, (I will not be checking my email until new year. Wishing everyone
here Happy Holidays)

View this message in context:
Sent from the Lucene - Java Users mailing list archive at<>.


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

Uwe Schindler
Achterdiek 19, 28357 Bremen
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message