[
https://issues.apache.org/jira/browse/SOLR-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415646#comment-17415646
]
Chris M. Hostetter commented on SOLR-15555:
-------------------------------------------
yeah, i haven't been able to repro either ... was hit on my linux laptop,
openjdk version "11.0.4", while running a full {{./gradlew check}}.
I screwed up saving the logs, but I remember they were very short for this test
– the only thing interesting was the 2 INFO log mesages (matching the 2
'actual' DocSet creations) from TestInjection.
If you're beasting this, i would suggest adding this to your test so if it does
fail you'll at least have stack traces in the logs of where the createDocSet
calls are coming form...
{code:java}
@org.apache.solr.util.LogLevel("org.apache.solr.util.TestInjection=DEBUG"){code}
I'll keep trying with some tweaks to the test to try and force more distinct
queries into the cache.
> 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
>
> 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]
