The first question I have is whether you're sorting and/or faceting on many unique string values? I'm guessing that sometime you are. So, some questions to help pin it down: 1> what fields are you sorting on? 2> what fields are you faceting on? 3> how many unique terms in each (see the solr admin page).
Best Erick On Wed, Jun 15, 2011 at 8:22 AM, Bernd Fehling <bernd.fehl...@uni-bielefeld.de> wrote: > Dear list, > > after getting OOM exception after one week of operation with > solr 3.2 I used MemoryAnalyzer for the heapdumpfile. > It looks like the fieldCache eats up all memory. > > Objects Shalow Heap > Retained Heap > org.apache.lucene.search.FieldCache 0 0 >>= 14,636,950,632 > org.apache.lucene.search.FieldCacheImpl 1 32 >>= 14,636,950,384 > org.apache.lucene.search.FieldCacheImpl$StringIndexCache 1 32 >>= 14,636,947,080 > org.apache.lucene.search.FieldCache$StringIndex 10 320 >>= 14,636,944,352 > java.lang.String[] 519 567,811,040 >>= 13,503,733,312 > char[] 81,766,595 11,604,293,712 >>= 11,604,293,712 > > fieldCache retains over 14g of heap. > > When looking on stats page under fieldCache the description says: > "Provides introspection of the Lucene FieldCache, this is **NOT** a cache > that is managed by Solr." > > So is this a jetty problem and not solr? > > Why is fieldCache growing and growing until OOM? > > Regards > Bernd >
