[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421659#comment-17421659
]
Mark Robert Miller commented on SOLR-15555:
-------------------------------------------
It’s only if you turn off async for the cache. That’s why Mike says he will
leave it as an expert option. I’m just saying that feels kind of trappy to me.
We don’t really have a good way to designate expert options that may fail with
some features. Hope they have the right config with our comments. And we don’t
have a great handle on what works and doesn’t - we just found these issues and
then turned testing that option off. So my question is more like, shouldn’t
this just currently not be a valid option?
> 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: 5h 40m
> 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]
