[
https://issues.apache.org/jira/browse/SOLR-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632752#comment-15632752
]
Yonik Seeley commented on SOLR-9712:
------------------------------------
If we go this route (which I think we should) then we probably also should:
- change the default maxWarmingSearchers to 1
- remove maxWarmingSearchers from our starting configs (it becomes pretty
advanced... most shouldn't need to worry about it)
- remove maxWarmingSearchers from the majority of our test configs - we'll
want the best test coverage on maxWarmingSearchers=1
- add an upgrade note encouraging removal of maxWarmingSearchers from your
config, unless you specifically know better
- document the change in behavior of course...
> 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
> Fix For: master (7.0), 6.4
>
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
