Hi,
We are using Solr 1.4 running 2 cores each containing ~90M documents. Each
core index size on the disk is ~ 120 G.
The machine is a 64-bit quad-core 64G RAM running Windows Server 2008.
Max heap size is set to 9G for the Tomcat process. Default caches are used.

Our queries are complex and involve  8 facet fields (3 of them are boolean)
and sorting on up 2 fields in addition to Solr score.
I noticed a new behavior that didn't happened before: the first core being
queried after startup answers all the queries, even the ones bringing ten
millions of the documents, while the other core (that was queried the
second) causes OutOfMemory exceptions for any query, even the "smallest"
one. The heap is shown as not fully used 6-5 G out of 9. This is very
strange because till recently both cores were working well, handling the
heaviest queries, while the heap usage was on 8 G.

Any ideas?

Thanks

Reply via email to