rg/confluence/display/solr/MBean+Request+Handler
what do you see in terms of insertions/hits/misses on all of the caches in
each of the above scenerios?
: Date: Fri, 25 Sep 2015 17:31:30 +0200
: From: Christian Reuschling
: Reply-To: solr-user@lucene.apache.org
: To: "solr-user@lucene.apache
Erick, Walter and all,
as I wrote, I am aware of the firstSearcher event, we tried it manually before
we choosed to enhance
the QuerySenderListener.
I think our usage scenario (I didn't wrote about it for simplicity) is a bit
different from yours,
what makes this necessary. We are implementing
Right.
I chose the twenty most frequent terms from our documents and use those for
cache warming. The list of most frequent terms is pretty stable in most
collections.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Sep 25, 2015, at 8:38 AM, Erick
That's what the firstSearcher event in solrconfig.xml is for, exactly the
case of autowarming Solr when it's just been started. The queries you put
in that event are fired only when the server starts.
So I'd just put my queries there. And you do not have to put a zillion
queries here. Start with o
Hey all,
we want to avoid cold start performance issues when the caches are cleared
after a server restart.
For this, we have written a SearchComponent that saves least recently used
queries. These are
written to a file inside a closeHook of a SolrCoreAware at server shutdown.
The plan is to p
