[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845258#comment-17845258
]
Andrzej Bialecki commented on SOLR-13350:
-----------------------------------------
This is caused by breaking the end-to-end tracking of request context in
{{{}SolrRequestInfo{}}}, which uses a thread-local deque to provide the same
context for both the main and all sub-requests. This tracking is needed to
setup the correct query timeout instance on the searcher ( {{QueryLimits}} )
for time-limited searches in the {{SolrIndexSearcher:727}} . However, now that
this method is executed in a separate "searcherCollector" thread the
{{SolrRequestInfo}} instance it obtains is empty because it doesn't match the
original thread that set it.
> 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: 11h 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
