[
https://issues.apache.org/jira/browse/SOLR-9712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631818#comment-15631818
]
Shalin Shekhar Mangar commented on SOLR-9712:
---------------------------------------------
bq. One needs a reliable "update this document and make it visible, and don't
return until it is visible" in conjunction with "let's not warm more than one
searcher at a time".
I thought the first part was the reason behind waitSearcher=true? Agreed that
we need to fix the second part. As David said, the commits should block by
default instead of happening concurrently. Otherwise we cannot easily reason
about memory consumption when multiple clients call commit.
> 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
>
>
> 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]
