[
https://issues.apache.org/jira/browse/SOLR-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925303#comment-17925303
]
ASF subversion and git services commented on SOLR-17648:
--------------------------------------------------------
Commit 021541af199ab09ce604adae2095efe5cf0f77d3 in solr's branch
refs/heads/branch_9x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=021541af199 ]
SOLR-17648: multiThreaded=true: changed queue implementation (#3155)
from unlimited to 1000 max, after which the caller thread will execute.
Didn't need the RejectedExecutionException avoidance hack anymore; Lucene 9.12
has it.
Configurable size: solr.search.multiThreaded.queueSize
(cherry picked from commit 861a7761707457a65a3736ecc274cff3c8cb56e5)
> multiThreaded: Remove obsolete RejectedExecutionException avoidance
> -------------------------------------------------------------------
>
> Key: SOLR-17648
> URL: https://issues.apache.org/jira/browse/SOLR-17648
> Project: Solr
> Issue Type: Task
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Lucene 9.12 fixed a RejectedExecutionException risk
> https://github.com/apache/lucene/pull/13622 in which
> RejectedExecutionException is caught and the task is run. This is done with a
> simple Executor wrapper in IndexSearcher's constructor. I propose we remove
> the hack/work-around in SolrIndexSearcher. This brings back a
> LinkedBlockingQueue, and queue size to determine.
--
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
