Michael, The servlet container controls timeouts, max threads and such. That's not a high query rate, but yes, it could be solr or OS caches are cold. You will ne able too see all this in SPM for Solr while you hammer your poor Solr servers :)
Otis Solr & ElasticSearch Support http://sematext.com/ On Oct 18, 2013 11:38 AM, "michael.boom" <my_sky...@yahoo.com> wrote: > I have a SolrCloud environment with 4 shards, each having a replica and a > leader. The index size is about 70M docs and 60Gb, running with Jetty + > Zookeeper, on 2 EC2 instances, each with 4CPUs and 15G RAM. > > I'm using SolrMeter for stress testing. > If I restart Jetty and then try to use SolrMeter to bomb an instance with > queries, using a query per minute rate of 3000 then that solr instance > somehow timesout and I need to restart it again. > If instead of using 3000 qpm i startup slowly with 200 for a minute or two, > then 1800 and then 3000 everything is good. > > I assume this happens because Solr is not warmed up. > What settings could I tweak so that Solr doesn't time out anymore when > getting many requests? Is there a way to limit how many req it can serve? > > > > ----- > Thanks, > Michael > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-timeout-after-reboot-tp4096408.html > Sent from the Solr - User mailing list archive at Nabble.com. >
