[ 
https://issues.apache.org/jira/browse/SOLR-17414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914252#comment-17914252
 ] 

Varun Thacker commented on SOLR-17414:
--------------------------------------

Just posting here to close the loop. 

A user on the lucene user mailing list had reported a vector query bug 
[https://lists.apache.org/thread/xn1xg5szxhrs0sbcy4gmx4cvohy6flvh. 
|https://lists.apache.org/thread/xn1xg5szxhrs0sbcy4gmx4cvohy6flvh]I have a 
local setup where I request `fl=score,sort=id desc` and export 10k rows out of 
a knn query and can reproduce this bug

So I started looking into this yesterday and here is my analysis
 # The issue reported was introduced in 9.7
 # The commit that caused it was 
[https://github.com/apache/solr/commit/cfec121bab2ecfc4c06e20a5533596025ae63d98]
 # Even though multi-threading is disabled by default, the collector manager 
executor changed for single threaded search in that commit. Still very unsure 
how that subtle change caused it.
 # However the good news is the changes made in this Jira actually fixes the 
issues reported by the user.

> 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]

Reply via email to