lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ravichandra <>
Subject Out of Memory Error while using WildCard Query
Date Fri, 02 Jan 2009 07:35:30 GMT


  I am using Lucene for record set of around 1.5 million records and the
index size is approximately 400MB. I am also using query level boosting so
that we can get the relevant records first in the search results.
  Here is the way I create query:

  Query partialMatchQuery = new WildcardQuery(new Term("column_name",

When I deployed the application on a tomcat instance with 512MB RAM. First
it threw an exception about too many clauses, so I set the Max clause count
to Integer max. Then it threw an out of memory error.

The options I tried:

•	I thought of using Filters, but I have to search on normal string data not
Dates. And I am not able to use the boosting with filters.

•	If I upgrade the RAM to 1GB, I didn’t get any out of memory error. But I
feel if the data gets increased, this error may come up again. 

1.	To my understanding, filters will be applied on the search results. Is it
2.	Is there any way we can use boost with filters?
3.	What should be the RAM size when compared with index size?
4.	If the index is loaded once into the memory, will it cater all the
requests or it has to load the index for each request? 
5.	Do I need to increase the RAM if the number of users increases?

Please suggest me how to over come this issue.


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

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

View raw message