[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417669#comment-17417669
]
Mike Drob commented on SOLR-15555:
----------------------------------
[~markrmiller] - you're probably missing
[https://github.com/apache/solr/pull/294] which came in later and defaulted
things to async. I wasn't thinking about all the Join queries initially, and
will leave sync option as an expert opt-in for now, but it probably needs to be
removed, especially considering that my JMH tests don't show much (any?)
difference between async and sync caches.
> Use filterCache.computeIfAbsent in SolrIndexSearcher
> ----------------------------------------------------
>
> Key: SOLR-15555
> URL: https://issues.apache.org/jira/browse/SOLR-15555
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Major
> Fix For: main (9.0), 8.10
>
> Attachments: OUTPUT-org.apache.solr.search.TestRangeQuery.txt.gz,
> SOLR-15555.test-fix.patch
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> When multiple concurrent queries come in at the same time, in several cases
> they can trigger concurrent computations of a DocSet for the cache. We should
> investigate where this happens and possibly take care to only do a single
> computation when possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
