[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735817#comment-17735817
]
Ishan Chattopadhyaya commented on SOLR-13350:
---------------------------------------------
[[email protected]], the ThreadSafeBitSet has a spin lock and compare and
set,
https://github.com/chatman/solr/blob/jira/solr-13350-9x/solr/core/src/java/org/apache/solr/search/ThreadSafeBitSet.java#L81-L89
How important is a thread safe bitset here? I am thinking that separate threads
will operate on disjoint regions within the same bitset, and likely never
collide on the same bits. Is that alone not sufficient to ensure consistency
under concurrent updates to the bitset, without cas loop or locking etc.?
> 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: 3h
> 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]
