[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415664#comment-17415664
]
Chris M. Hostetter commented on SOLR-15555:
-------------------------------------------
I think the problem is just that the test is setting
{{TestInjection.delayBeforeCreatingNewDocSet}} too early, so that the
{{createIndex()}} call also includes that delay – which means if there are any
cached queries in the existing SolrIndexSearcher, tey get the delay on warm –
and contribute to the {{TestInjection.countDocSetDelays}} even though those
queries may have nothing to do with this test invocation.
When using {{-Ptests.iters=5 --tests
TestRangeQuery.testRangeQueryWithFilterCache}} this can be easily problematic –
but even if we're just running every test method once, the method ordering
might mean that {{testRangeQueryWithFilterCache}} gets run right after some
other method that happened to leave a range query in the cache that will be
warmed by {{testRangeQueryWithFilterCache}} 's call to {{createIndex()}} –
throwing off the count.
> 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
>
> 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]
