[
https://issues.apache.org/jira/browse/SOLR-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-9712:
-------------------------------
Attachment: SOLR-9712.patch
OK, here's the final patch that I'll probably commit tomorrow. Most
maxWarmingSearcher specifications have been removed from test configurations.
This doesn't really reduce coverage much due to the fact that
maxWarmingSearchers=1 (the default) is not special-cased so all code paths will
still be exercised with concurrent commits.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
