Hello, Is this bug with Solr with Java 17 specific to HotSpot-based JVMs ?
FYI I'm running Solr 8.11.2 in production for a while with IBM Semeru 17 (based on OpenJ9 JVM) on CentOS 7.9 x64, and I have not observed such crashes. Alex Le mar. 25 oct. 2022 à 10:32, Jan Høydahl <jan....@cominvent.com> a écrit : > > Several users running Solr in production on OpenJDK 17 or later have > experienced JVM crashes due to a known bug in the JDK. Read more about the > bug in SOLR-16463[1]. > > Known mitigations are to either downgrade to JDK 11 or to start Solr with a > Java startup flag that avoids the failure condition. Here is how to manually > apply the flag: > > Edit your solr.in.sh or solr.in.cmd file to set the SOLR_OPTS environment > variable as follows: > > Linux: > SOLR_OPTS=-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put > > Windows: > SET > SOLR_OPTS=-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put > > Alternatively, you can inject the same flag with the -a argument, e.g: > bin/solr -a > "-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put" > > If you run Solr 9 with the official Docker image, we have already pushed an > updated Docker image to Docker Hub that will inject the flag for you. Just > pull the image again to get it. The Docker image uses the -a option to set > this java flag when running Solr, so if you are using the -a option you will > need to provide the JVM flag mentioned above in addition to the other flags > you are setting. > > [1]: https://issues.apache.org/jira/browse/SOLR-16463 > > Read this news on the web page: > https://solr.apache.org/news.html#java-17-bug-affecting-solr
