[
https://issues.apache.org/jira/browse/SOLR-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-16463:
-------------------------------
Description:
Solr 9+ under JDK 17+ may crash frequently, during JVM Hotspot optimization of
caffeine cache class.
This is due to a JDK bug
([https://bugs.openjdk.org/browse/JDK-8285835|https://bugs.openjdk.org/browse/JDK-8285835)]),
but may not be fixed soon in JDK17, so we should make a workaround to protect
our users. The bug is also reported in caffeine project
([https://github.com/ben-manes/caffeine/issues/797]).
So there are a few possible ways to avoid this
* Run Solr 9 on JDK 11
* Do not use caffeine cache, find some replacement
* Caffeine cache releases a new version that do not suffer the issue, and solr
uses that
* Instruct JDK to not optimize that class, using JDK option
{{-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put}}
See users list for examples of this issue seen in the wild:
[https://lists.apache.org/thread/wg7qtkddd1t5h08okj7gm9qbrpdf0ox6]
Docker users can set SOLR_OPTS with the JDK option above. Patching the official
Dockerfile to include this may be the least intrusive fix short-term. We should
also document the issue on website and perhaps docker hub to provide users with
a workaround.
For 9.1 we can hardcode the JDK flag in bin/solr.
was:
Solr 9+ under JDK 17+ may crash frequently, during JVM Hotspot optimization of
caffeine cache class.
This is due to a JDK bug
([https://bugs.openjdk.org/browse/JDK-8285835|https://bugs.openjdk.org/browse/JDK-8285835)]),
but may not be fixed soon in JDK17, so we should make a workaround to protect
our users. The bug is also reported in caffeine project
([https://github.com/ben-manes/caffeine/issues/797]).
So there are a few possible ways to avoid this
* Run Solr 9 on JDK 11
* Do not use caffeine cache, find some replacement
* Caffeine cache releases a new version that do not suffer the issue, and solr
uses that
* Instruct JDK to not optimize that class, using
Due to a known bug in current JDK 17 and later (see
[https://lists.apache.org/thread/wg7qtkddd1t5h08okj7gm9qbrpdf0ox6] and
[)|https://bugs.openjdk.org/browse/JDK-8285835)] due o Hotspot JIT
optimization o.
in e.g. a kubernetes environent.
A known workaround is to build your own Solr docker image on JRE11. Let's
provide a convenience official image on temurin11 for 9.0 users, and consider
it for the upcoming 9.1 release too if the issue is not resolved by then.
> Serious crash on JDK17+ due to JIT on caffeinecache
> ---------------------------------------------------
>
> Key: SOLR-16463
> URL: https://issues.apache.org/jira/browse/SOLR-16463
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Docker
> Affects Versions: 9.0
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Blocker
> Fix For: 9.1
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Solr 9+ under JDK 17+ may crash frequently, during JVM Hotspot optimization
> of caffeine cache class.
> This is due to a JDK bug
> ([https://bugs.openjdk.org/browse/JDK-8285835|https://bugs.openjdk.org/browse/JDK-8285835)]),
> but may not be fixed soon in JDK17, so we should make a workaround to
> protect our users. The bug is also reported in caffeine project
> ([https://github.com/ben-manes/caffeine/issues/797]).
> So there are a few possible ways to avoid this
> * Run Solr 9 on JDK 11
> * Do not use caffeine cache, find some replacement
> * Caffeine cache releases a new version that do not suffer the issue, and
> solr uses that
> * Instruct JDK to not optimize that class, using JDK option
> {{-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put}}
> See users list for examples of this issue seen in the wild:
> [https://lists.apache.org/thread/wg7qtkddd1t5h08okj7gm9qbrpdf0ox6]
> Docker users can set SOLR_OPTS with the JDK option above. Patching the
> official Dockerfile to include this may be the least intrusive fix
> short-term. We should also document the issue on website and perhaps docker
> hub to provide users with a workaround.
> For 9.1 we can hardcode the JDK flag in bin/solr.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
