lucene-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/SOLR-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754990#comment-15754990
] 

Yonik Seeley commented on SOLR-9712:
------------------------------------

Nope... I hadn't realized we had a good reproducible test for that.
Looks like that test expects to hit an exception though, so it would need to be tweaked to
pass now.

> Saner default for maxWarmingSearchers
> -------------------------------------
>
>                 Key: SOLR-9712
>                 URL: https://issues.apache.org/jira/browse/SOLR-9712
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: search
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Yonik Seeley
>             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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message