[
https://issues.apache.org/jira/browse/LUCENE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845822#comment-16845822
]
Atri Sharma commented on LUCENE-8808:
-------------------------------------
[~jpountz] If a shared executor is used across all IndexSearchers, then there
is a probability that a few odd large queries will hog all available threads on
the executor, and the remaining queries can be queued in the executor's queue.
This parameter is an effort to ensure that a small subset of queries does not
overload the shared resource.
> Introduce Optional Cap on Number Of Threads Per Query
> -----------------------------------------------------
>
> Key: LUCENE-8808
> URL: https://issues.apache.org/jira/browse/LUCENE-8808
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Atri Sharma
> Priority: Major
>
> With the presence of https://issues.apache.org/jira/browse/LUCENE-8757 , a
> natural progression is to allow advanced users to specify a cap on the number
> of threads a query can use. This is especially useful for long polled
> IndexSearcher instances, where the same instance is used to fire queries for
> multiple runs and there are multiple concurrent IndexSearcher instances on
> the same node.
>
> This will be an optional parameter and local only to the IndexSearcher
> instance being configured during construction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
