exceeding max warming searchers and failing to open a searcher are entirely different things.
Your problem is more severe. Have any more logs? There should likely be deeper stack traces telling why the Searcher could not be opened. - Mark On Mar 12, 2013, at 12:41 AM, mark12345 <marks1900-pos...@yahoo.com.au> wrote: > I am running into issues where my Solr instance is behaving weirdly. After I > get the SolrException "Error opening new searcher", my Solr instance fails > to handle even the simplest of update requests. > > >> http://lucene.472066.n3.nabble.com/exceeded-limit-of-maxWarmingSearchers-td494732.html > > I have found some suggestions that tend to suggest that I am making more > Solr commit requests than what my instance can handle, though I am unsure on > the way forward. What is really annoying is that I seem to have to restart > my Solr instance (service tomcat7 restart) to get things working again. I > am very concerned about this behaviour, as it seems that if I was to get a > spike in demand, the whole instance could fall down. > > Any suggestions on the way forward? > > > --------- > > 14:30:00 SEVERE SolrCore org.apache.solr.common.SolrException: > Error > opening new searcher > 14:30:00 SEVERE SolrDispatchFilter > null:org.apache.solr.common.SolrException: Error opening new searcher > > -- On Tomcat Solr restart -- > > 14:31:19 WARNING UpdateLog Starting log replay > tlog{file=/opt/solr/instances/solr/collection1/data/tlog/tlog.0000000000000017502 > refcount=2} active=false starting pos=0 > 14:31:20 WARNING UpdateLog Log replay finished. > recoveryInfo=RecoveryInfo{adds=2 deletes=0 deleteByQuery=0 errors=0 > positionOfStart=0} > > --------- > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrException-Error-opening-new-searcher-tp4046543.html > Sent from the Solr - User mailing list archive at Nabble.com.
