[
https://issues.apache.org/jira/browse/SOLR-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923016#comment-17923016
]
David Smiley commented on SOLR-17414:
-------------------------------------
Lucene 9.12 has a fix for this -- 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
I remove the hack/work-around here in favor leaning on Lucene's solution --
less for us to maintain. This brings back a queue size to determine.
> multiThreaded=true can result in RejectedExecutionException
> -----------------------------------------------------------
>
> Key: SOLR-17414
> URL: https://issues.apache.org/jira/browse/SOLR-17414
> Project: Solr
> Issue Type: Bug
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Fix For: 9.8
>
> Attachments: build-out2.txt
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Since the new multiThreaded search feature landed, I see a new test
> failure involving "RejectedExecutionException" being thrown
> [link|https://ge.apache.org/s/5ack462ji4mlu/tests/task/:solr:core:test/details/org.apache.solr.search.TestRealTimeGet/testStressGetRealtime?top-execution=1].
> It is thrown at a low level in Lucene building TermStates
> concurrently. I doubt the problem is specific to that test
> (TestRealTimeGet) but that test might induce more activity than most
> tests, thus crossing some thresholds like the queue size -- apparently
> 1000.
> *I don't think we should be throwing a RejectedExecutionException
> when running a Search query*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
