[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848668#comment-17848668
]
Andrzej Bialecki commented on SOLR-13350:
-----------------------------------------
{quote}As of now, the timeAllowed requests are anyway executed without
multithreading
{quote}
This is based on a {{QueryCommand.timeAllowed}} flag that is set only from the
{{timeAllowed}} param. However, this concept was extended in SOLR-17138 to
{{QueryLimits}} that is now initialized also using other params. There is
indeed some inconsistency here that's a left-over from that change, in the
sense that `QueryCommand.timeAllowed` should have been either removed
completely or replaced with something like {{{}queryLimits{}}}, to make sure to
check the current SolrRequestInfo for QueryLimits.
In any case, the minimal workaround for this could be to check
{{QueryLimits.getCurrentLimits().isLimitsEnabled()}} instead of
{{{}QueryCommand.timeAllowed{}}}. But a better fix would be to properly unbreak
the tracking of the parent {{SolrRequestInfo}} in MT search.
> 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: 11.5h
> 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]
