You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2006/12/22 05:24:20 UTC
[jira] Created: (SOLR-91) autowarming searchers can stack up
autowarming searchers can stack up
----------------------------------
Key: SOLR-91
URL: http://issues.apache.org/jira/browse/SOLR-91
Project: Solr
Issue Type: Improvement
Affects Versions: 1.1.0
Reporter: Yonik Seeley
If the commit frequency is high, and autowarming of caches is 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SOLR-91) autowarming searchers can stack up
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SOLR-91?page=comments#action_12460379 ]
Yonik Seeley commented on SOLR-91:
----------------------------------
A bad solution would be to kill the oldest searcher... this strategy could lead to starvation.
A better solution: allow a <commit/> to fail after a configurable threshold of the number of warming searchers is reached.
Downsides:
- commit currently does not fail (unless exceptional circumstances like an IOError)
- If enabled on a master, two different clients doing a quick add+commit
could now cause failure. We could either just recommend it never be enabled for a master, or
some autocommit functionality could be added to enforce a minimum wait time between commits.
> autowarming searchers can stack up
> ----------------------------------
>
> Key: SOLR-91
> URL: http://issues.apache.org/jira/browse/SOLR-91
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Yonik Seeley
>
> If the commit frequency is high, and autowarming of caches is 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-91) warming searchers can stack up
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SOLR-91?page=all ]
Yonik Seeley updated SOLR-91:
-----------------------------
Summary: warming searchers can stack up (was: autowarming searchers can stack up)
Description:
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.
was:
If the commit frequency is high, and autowarming of caches is 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.
> warming searchers can stack up
> ------------------------------
>
> Key: SOLR-91
> URL: http://issues.apache.org/jira/browse/SOLR-91
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Yonik Seeley
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SOLR-91) warming searchers can stack up
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley updated SOLR-91:
-----------------------------
Attachment: maxWarmingSearchers.patch
> 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
[jira] Resolved: (SOLR-91) warming searchers can stack up
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley resolved SOLR-91.
------------------------------
Resolution: Fixed
committed.
> 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
[jira] Commented: (SOLR-91) warming searchers can stack up
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ 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