You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Vassil Velichkov (Jira)" <ji...@apache.org> on 2023/01/07 05:16:00 UTC

[jira] [Comment Edited] (SOLR-16463) Serious crash on JDK17+ due to JIT on caffeinecache

    [ https://issues.apache.org/jira/browse/SOLR-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655649#comment-17655649 ] 

Vassil Velichkov edited comment on SOLR-16463 at 1/7/23 5:15 AM:
-----------------------------------------------------------------

It seems the OpenJDK bug is fixed, the ticket is awaiting for review and hopefully the pull request will be merged and will be included in the next patch version:

[https://bugs.openjdk.org/browse/JDK-8285835?focusedCommentId=14548280&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14548280]


was (Author: vassil.velichkov):
It seems the OpenJDK bug is fixed, the ticket waits for review and hopefully it will be including in the next patch version:

https://bugs.openjdk.org/browse/JDK-8285835?focusedCommentId=14548280&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14548280

> 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: 4h
>  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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org