Hi Rashi, abnormal behaviour depends on your data, system and work load - I have seen abnormal behaviour at customers sites and it turned out to be a miracle that they the customer had no serious problems before :-)
* running out of sockets - you might need to check if you have enough sockets (system quota) and that the sockets are closed properly (mostly a Windows/networking issue - CLOSED_WAIT) * understand your test setup - usually a test box is much smaller in terms of CPU/memory than you production box ** you might be forced to tweak your test configuration (e.g. production SOLR cache configuration can overwhelm a small server) * understand your work-load ** if you have long-running queries within your performance tests they tend to bring down your server under high-load and your “abnormal” condition looks very normal at hindsight ** spot your long-running queries, optimise them, re-run your tests ** check your cache warming and how fast you start your load injector threads Cheers, Siegfried Goeschl On 13 Jul 2014, at 09:53, rashi gandhi <gandhirash...@gmail.com> wrote: > Hi, > > I am using SolrMeter for load/stress testing solr performance. > Tomcat is configured with default "maxThreads" (i.e. 200). > > I set Intended Request per min in SolrMeter to 1500 and performed testing. > > I found that sometimes it works with this much load on solr but sometimes > it gives error "Sever Refused Connection" in solr. > On getting this error, i increased maxThreads to some higher value, and > then it works again. > > I would like to know why solr is behaving abnormally, initially when it was > working with maxThreads=200. > > Please provide me some pointers.
