[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843841#comment-17843841
]
Ishan Chattopadhyaya commented on SOLR-13350:
---------------------------------------------
bq. Do we have a limited queue for the pool, leading to the
"RejectedExecution"? I think we'd like a caller-runs policy so we don't wait &
starve
Changed it to a larger queue than then number of threads, and removed the
rejected execution handler as well.
bq. Commit ff6607d25f023a59f866a66820037bb215342ca8 in solr's branch
refs/heads/main from Ishan Chattopadhyaya
Will backport to branch_9x after a few days of baking on main.
> 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: 10h 40m
> 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
