Currently , once solr is started, we run a batch that would fire queries to solr ( just something like the firstsearcher does). Once this is done, then the users would start using search.
In case the server is restarted or anything crashes, then again i have to run this batch which i cannot control. Thats why if there is any way we can persist . This was only for our business scenario. Thanks, Prasi On Wed, Nov 27, 2013 at 2:05 PM, michael.boom <my_sky...@yahoo.com> wrote: > Caches are only valid as long as the Index Searcher is valid. So, if you > make > a commit with opening a new searcher then caches will be invalidated. > However, in this scenario you can configure your caches so that the new > searcher will keep a certain number of cache entries from the previous one > (autowarmCount). > That's the only cache "persistence" Solr can offer. On restarting/crash you > can't reuse caches. > > Why do you need to persist caches in case of a crash? What's your usage > scenario? > Do you have problems with performance after startup? > > You can read more at http://wiki.apache.org/solr/SolrCaching#Overview > > > > ----- > Thanks, > Michael > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Persist-solr-cache-tp4103463p4103469.html > Sent from the Solr - User mailing list archive at Nabble.com. >
