[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832907#comment-17832907
]
Ishan Chattopadhyaya commented on SOLR-13350:
---------------------------------------------
I think I understand what is going on:
This issue in Lucene now uses the provided threadpool that Solr passes to the
searcher to spawn concurrent sub-tasks for building the term states:
https://github.com/apache/lucene/pull/12183
However, this leads to starvation, because once all threads are executing user
queries, there are no free threads in the threadpool to spawn more tasks for
building these term states.
Related issue (but not the cause) for this is:
https://github.com/apache/lucene/commit/2106bf5172a9c38a8457db383eb9f5cd1918ddc5
> Explore collector managers for multi-threaded search
> ----------------------------------------------------
>
> Key: SOLR-13350
> URL: https://issues.apache.org/jira/browse/SOLR-13350
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SOLR-13350.patch, SOLR-13350.patch, SOLR-13350.patch
>
> Time Spent: 7h 10m
> Remaining Estimate: 0h
>
> AFAICT, SolrIndexSearcher can be used only to search all the segments of an
> index in series. However, using CollectorManagers, segments can be searched
> concurrently and result in reduced latency. Opening this issue to explore the
> effectiveness of using CollectorManagers in SolrIndexSearcher from latency
> and throughput perspective.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
