While indexing, several SearchStax Managed Search service clients have encountered an error like this one:
Error from server at http://10.35.9.135:8983/solr/shard1_replica1: Error opening new searcher. exceeded limit of maxWarmingSearchers=2, try again later.
The key is this phrase:
exceeded limit of maxWarmingSearchers=2From Apache.org:
Whenever a commit happens in Solr, a new “searcher” (with new caches) is opened, “warmed” up according to your SolrConfigXml settings, and then put in place. The previous searcher is not closed until the “warming” search is ready. If multiple commits happen in rapid succession, then a searcher may still be warming up when another commit comes in. This will cause multiple searchers to be started and warming at the same time, all competing for resources. Only one searcher is ever actively handling queries at a time – all old searchers are thrown away when the latest one finishes warming.
maxWarmingSearchers is a setting in SolrConfigXml that helps you put a safety valve on the number of overlapping warming searchers that can exist at one time. If you see this error it means Solr prevented a new searcher from being opened because there were already X searchers warming up.
The best way to prevent this log message is to reduce the frequency of commit operations. Enough time should pass between commits for each commit to completely finish.”
The remedy is not to increase the number of warming searchers, but to decrease the frequency of commits.
Questions?
Do not hesitate to contact the SearchStax Support Desk.