[
https://issues.apache.org/jira/browse/SOLR-16548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633997#comment-17633997
]
Shawn Heisey commented on SOLR-16548:
-------------------------------------
Problem is also happening with the techproducts example.
Next I will try 8.11.2.
> CaffeineCache seems to be not working in 9.0 and later
> ------------------------------------------------------
>
> Key: SOLR-16548
> URL: https://issues.apache.org/jira/browse/SOLR-16548
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 9.0, 9.1, 9.2
> Reporter: Shawn Heisey
> Priority: Major
>
> I am seeing evidence that CaffeineCache is not working correctly.
> To reproduce:
> * download 9.0.0, extract it, and cd into the extracted directory. Do this
> on a system that is not already running any software (including Solr) that
> listens on ports 8983 or 7574.
> * Start the cloud example with this command:
> ** {{SOLR_JETTY_HOST=0.0.0.0 bin/solr -e cloud -noprompt}}
> * Visit this URL in your browser, substituting "hostname" with a name or IP
> address that is correct for your environment:
> **
> [http://hostname:8983/solr/#/gettingstarted_shard1_replica_n6/plugins?type=cache&entry=filterCache]
> * In another tab, visit this URL, substituting hostname again:
> **
> [http://hostname:8983/solr/gettingstarted_shard1_replica_n6/select?q=*:*&fq=id:test]
> * On that tab, hold shift and press the reload button. Do this several times.
> * Go back to the first tab and reload the page.
> You will see that size, lookups, and inserts are 1, but hits is zero. Both
> hits and lookups should be increasing with every shift-reload on the other
> tab.
> Is this a valid test? I think it should be.
> I am running with OpenJDK 11. For 9.1.0 and 9.2.0-SNAPSHOT, I am building
> with OpenJDK 11 as well. This should mean that the caffeine-related
> mitigation for crashing on Java 17 is not enabled.
> On branch_9x, I have tried downgrading Caffeine from 3.1.1 to 3.0.5 and also
> to 2.9.2 and it did not change the behavior, so I don't think the problem is
> in Caffeine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
