[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831454#comment-16831454
]
Ishan Chattopadhyaya commented on SOLR-13350:
---------------------------------------------
Updated patch with the following:
# Added an executor service (which is used for the multi-threaded search).
# TODO: JoinQParserPlugin closes the "from core" on every thread of the search
(using a close hook). This causes problems with multiple core close calls for
the same request. Tried to handle it naively for now (to make the tests pass).
Does someone have ideas to tackle it properly?
# TODO: Add a parameter to selectively enable multi-threaded search. Use that
parameter randomly with tests.
Right now, except the Join tests (esp. TestCrossCoreJoin), all pass.
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SOLR-13350.patch, SOLR-13350.patch, SOLR-13350.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
