[
https://issues.apache.org/jira/browse/SOLR-16707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702995#comment-17702995
]
Michael Gibney commented on SOLR-16707:
---------------------------------------
I think that happens externally, [in
SolrIndexSearcher|https://github.com/apache/solr/blob/bfccca2837e3f1625145454e75e2d602689f3781/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java#L958-L973].
I interpret the above snippet means "you can configure a cache {{async=true}},
but it won't actually be computed async if you have timeout enabled".
So iiuc this is not actually a reason to configure a cache {{async=false}} --
{{async=true}} caches can definitely have timeout enabled, it just won't be
particularly helpful in the way that one might hope {{async=true}} would be.
> TestFiltering.testRandomFiltering Caffeine cache async=false
> IllegalStateException: Recursive update
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-16707
> URL: https://issues.apache.org/jira/browse/SOLR-16707
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mikhail Khludnev
> Priority: Minor
>
> see the linked mail thread.
> There are systematic test failures with async=false.
> Why can't we just turn `async=true` for this test and others?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
