A quick ping on this. To give more stats, I have 100's of collections on
every node. The time it takes for one collection to boot up /loadonStartup
is around 10-20 seconds ("and sometimes even 1 minute). I do not have any
query auto warming etc. On a per collection basis I load a bunch of
libraries (for custom analyzer plugins) to compute the classpath. That
might be a reason for the high boot up timeMy solrconfig.xml entry is as follows <lib dir="/mnt/solr/lib/" regex=".*\.jar" /> Every core that boots up seems to be loading all jars over and over again. Is there a way to ask solr to load all jars only once? Thanks - Nitin On Wed, Feb 26, 2014 at 3:06 PM, KNitin <nitin.t...@gmail.com> wrote: > Thanks, Shawn. I will try to upgrade solr soon > > Reg firstSearcher: I think it does nothing now. I have configured to use > ExternalFileLoader but there the external file has no contents. Most of the > queries hitting the collection are expensive and tail queries. What will be > your recommendation to warm the first Searcher/new Searcher? > > Thanks > Nitin > > > On Tue, Feb 25, 2014 at 4:12 PM, Shawn Heisey <s...@elyograg.org> wrote: > >> On 2/25/2014 4:30 PM, KNitin wrote: >> >>> Jeff : Thanks. I have tried reload before but it is not reliable >>> (atleast >>> in 4.3.1). A few cores get initialized and few dont (show as just >>> recovering or down) and hence had to move away from it. Is it a known >>> issue >>> in 4.3.1? >>> >> >> With Solr 4.3.1, you are running into this bug with reloads under >> SolrCloud: >> >> https://issues.apache.org/jira/browse/SOLR-4805 >> >> The only way to recover from this bug is to restart Solr.The bug is fixed >> in 4.4.0 and later. >> >> >> Shawn,Otis,Erick >>> >>> Yes I have reviewed the page before and have given 1/4 of my mem to JVM >>> and the rest to RAM/Os Cache. (15 Gb heap and 45 G to rest. Totally 60G >>> machine). I have also reviewed the tlog file and they are in the order of >>> KB (4-10 or 30). I have SSD and the reads are hardly noticable (in the >>> order of 100Kb during that time frame). I have also disabled swap on all >>> machines >>> >>> Regarding firstSearcher, It is currently set to externalFileLoader. What >>> is >>> the use of first searcher? I havent played around with it >>> >> >> I don't think it's a good idea to have extensive warming queries. I do >> exactly one query in firstSearcher and newSearcher: a query for all >> documents with zero rows, sorted on our most common sort field. This is >> designed purely to preload the sort data into the FieldCache. >> >> Thanks, >> Shawn >> >> >
