lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-9712) Saner default for maxWarmingSearchers
Date Fri, 16 Dec 2016 03:58:58 GMT


Yonik Seeley commented on SOLR-9712:

OK, how about this?
maxWarmingSearchers now defaults to 1, and more importantly commits will now *block* if this
limit is exceeded instead of throwing an exception (a good thing). Consequently there is no
longer a risk in overlapping commits. Nonetheless users should continue to avoid excessive
committing.  Users are advised to remove any pre-existing maxWarmingSearchers entries from
their solrconfig.xml files.

> Saner default for maxWarmingSearchers
> -------------------------------------
>                 Key: SOLR-9712
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: search
>            Reporter: Shalin Shekhar Mangar
>             Fix For: master (7.0), 6.4
>         Attachments: SOLR-9712.patch, SOLR-9712.patch, SOLR-9712.patch
> As noted in SOLR-9710, the default for maxWarmingSearchers is Integer.MAX_VALUE which
is just crazy. Let's have a saner default. Today we log a performance warning when the number
of on deck searchers goes over 1. What if we had the default as 1 that expert users can increase
if needed?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message