[
https://issues.apache.org/jira/browse/SOLR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463450
]
Yonik Seeley commented on SOLR-91:
----------------------------------
OK, maxWarmingSearchers defines the max number of background warming searchers.
Exceed it, and you get a 503 (which goes in the XML, not in the HTTP response
code, but that's a different issue):
$ curl http://localhost:8983/solr/update -i -d '<commit/>'
HTTP/1.1 200 OK
Date: Wed, 10 Jan 2007 01:05:41 GMT
Server: Jetty/5.1.11RC0 (Windows XP/5.1 x86 java/1.5.0_09
Content-Type: text/xml; charset=UTF-8
Content-Length: 115
<result status="503">Error opening new searcher. exceeded limit of maxWarmingSea
rchers=2, try again later.</result>
if missing in the config, the default is as before (unlimited).
I set it to 4 in the example config as a happy medium between searchers and
masters.
> warming searchers can stack up
> ------------------------------
>
> Key: SOLR-91
> URL: https://issues.apache.org/jira/browse/SOLR-91
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Yonik Seeley
> Attachments: maxWarmingSearchers.patch
>
>
> If the commit frequency is high, and searcher warming configured, sometimes
> an overlap of warming searchers can occur. Solr currently detects this and
> logs a warning message.
> While normally relatively harmless, multiple warming searchers can sometimes
> cause thrashing, extending the time it takes to complete warming, and causing
> a chain reaction where more and more searchers try to warm concurrently.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
