You'll want to check to see if there are any static warming queries being run as well.
How often are you committing and opening a new searcher? Are you using autoCommits or explicitly committing? Joel Bernstein http://joelsolr.blogspot.com/ On Wed, Aug 12, 2015 at 3:57 AM, Adrian Liew <adrian.l...@avanade.com> wrote: > Additionally, > > I realized that my autowarmCount is set to zero for the following Cache > entries except perSegFilter: > > <filterCache class="solr.FastLRUCache" > size="512" > initialSize="512" > autowarmCount="0"/> > > <!-- 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. > Additional supported parameter by LRUCache: > maxRamMB - the maximum amount of RAM (in MB) that this cache is > allowed > to occupy > --> > <queryResultCache class="solr.LRUCache" > size="512" > initialSize="512" > autowarmCount="0"/> > > <!-- 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="512" > initialSize="512" > autowarmCount="0"/> > > <!-- custom cache currently used by block join --> > <cache name="perSegFilter" > class="solr.search.LRUCache" > size="10" > initialSize="0" > autowarmCount="10" > regenerator="solr.NoOpRegenerator" /> > > > The link, > https://wiki.apache.org/solr/FAQ#What_does_.22PERFORMANCE_WARNING:_Overlapping_onDeckSearchers.3DX.22_mean_in_my_logs.3F > did suggest to reduce the autowarmCount or reduce warm up cache activity > (which I am not sure where to begin doing this). > > I suspect autowarmCount is not very large as the above. > > Let me know what you think. > > Best regards, > Adrian Liew > > > -----Original Message----- > From: Adrian Liew [mailto:adrian.l...@avanade.com] > Sent: Wednesday, August 12, 2015 3:32 PM > To: solr-user@lucene.apache.org > Subject: RE: Performance warning overlapping onDeckSearchers > > Thanks Shawn. Having said that increasing maxWarmingSearchers is usually > wrong to solve this, are there any implications if we set > maxWarmingSearchers to zero to resolve this problem? > > Or do you think there are some other settings that are worthwhile tuning > to cater to the above? > > Best regards, > Adrian > > -----Original Message----- > From: Shawn Heisey [mailto:apa...@elyograg.org] > Sent: Tuesday, August 11, 2015 11:02 PM > To: solr-user@lucene.apache.org > Subject: Re: Performance warning overlapping onDeckSearchers > > On 8/11/2015 3:02 AM, Adrian Liew wrote: > > Has anyone come across this issue, [some_index] PERFORMANCE WARNING: > Overlapping onDeckSearchers=2? > > > > I am currently using Solr v5.2.1. > > > > What does this mean? Does this raise red flags? > > > > I am currently encountering an issue whereby my Sitecore system is > unable to update the index appropriately. I am not sure if this is linked > to the warnings above. > > > https://wiki.apache.org/solr/FAQ#What_does_.22PERFORMANCE_WARNING:_Overlapping_onDeckSearchers.3DX.22_mean_in_my_logs.3F > > What the wiki page doesn't explicitly state is that increasing > maxWarmingSearchers is usually the wrong way to solve this, because that > can actually make the problem *worse*. It is implied by the things the > page DOES say, but it is not stated. > > Thanks, > Shawn > >
