[
https://issues.apache.org/jira/browse/SOLR-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620163#comment-17620163
]
Uwe Schindler commented on SOLR-16463:
--------------------------------------
Instead of creating a custom docker image, you could do the following as
fallback. Just use JDK 17 and add the following to the Java startup command
line:
{{-XX:CompileCommand=exclude,com.github.benmanes.caffeine.cache.BoundedLocalCache::put}}
This will prevent that the problematic method is compiled. Maybe just update
the Docker image and add this command line option. It may make the cache a bit
slower, but I don't thing this has much effect, because the method does not
seem to be "hot", otherwise the bug would happen after latest 5 minutes runtime
of Solr.
> Provide a jre11 version of Solr 9.0 docker image
> ------------------------------------------------
>
> Key: SOLR-16463
> URL: https://issues.apache.org/jira/browse/SOLR-16463
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Docker
> Affects Versions: 9.0
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Due to a known bug in current JDK 17 (see
> [https://lists.apache.org/thread/wg7qtkddd1t5h08okj7gm9qbrpdf0ox6] and
> [https://bugs.openjdk.org/browse/JDK-8285835)] Solr 9.0 under temurin17 may
> crash frequently 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
