lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <>
Subject Re: solr indexing warning
Date Fri, 20 Nov 2015 06:45:01 GMT
On 11/19/2015 11:06 PM, Midas A wrote:
> <filterCache class="solr.FastLRUCache" size="5000" initialSize="5000"
> autowarmCount="1000"/> <!-- Query Result Cache Caches results of searches -
> ordered lists of document ids (DocList) based on a query, a sort, and the
> range of documents requested. --> <queryResultCache class="solr.LRUCache"
> size="1000" initialSize="1000" autowarmCount="1000"/> <!-- Document Cache
> Caches Lucene Document objects (the stored fields for each document). Since
> Lucene internal document ids are transient, this cache will not be
> autowarmed. --> <documentCache class="solr.LRUCache" size="1000" initialSize
> ="1000" autowarmCount="1000"/>

Your caches are quite large.  More importantly, your autowarmCount is
very large.  How many documents are in each of your cores?  If you check
the Plugins/Stats area in the admin UI for your core(s), how many
entries are actually in each of those three caches?  Also shown there is
the number of milliseconds that it took for each cache to warm.

The documentCache cannot be autowarmed, so that config is not doing

When a cache is autowarmed, what this does is look up the key for the
top N entries in the old cache, which contains the query used to
generate that cache entry, and executes each of those queries on the new
index to populate the new cache.

This means that up to 2000 queries are being executed every time you
commit and open a new searcher.  The actual number may be less, if the
filterCache and queryResultCache are not actually reaching 1000 entries
each.  Autowarming can take a significant amount of time when the
autowarmCount is high.  It should be lowered.


View raw message