We encountered the same bug in SolrCloud deployment on our staging environment. We run Solr in Kubernetes and we use the official solr:9.0.0 docker image.
If this is a know bug in JDK that especially affects Lucene projects (and by proxy, Solr) why does the official Solr image use Java 17? Tomasz > On 11. Oct 2022, at 15:27, Kevin Risden <kris...@apache.org> wrote: > > https://lists.apache.org/thread/tbjljn512k8srtgr5f4tb2q6dmq1z515 > > This same issue was found in Lucene back in May and there was a JDK bug > opened about it. I think https://bugs.openjdk.org/browse/JDK-8285835 is > tracking this currently. > > Kevin Risden > > > On Mon, Oct 10, 2022 at 9:41 PM dmitri maziuk <dmitri.maz...@gmail.com> > wrote: > >> On 2022-10-10 4:58 PM, Jen-Ya Ku wrote: >>> Hi all, >>> >>> We've deployed solr9 on OpenJDK 17 and it crashed after few hours with >>> following error: >>> # A fatal error has been detected by the Java Runtime Environment: >>> # >>> # SIGSEGV (0xb) at pc=0x00007f834389b332, pid=8997, tid=9025 >> >> What are you running it on? -- E.g. some SuperMicro motherboards ship >> with fan speed set to "balanced" in the BIOS and have no thermal sensors >> under the RAM banks. Can you guess what happens when a memory-intensive >> job comes along and runs long enough for the SIMMS to heat up? >> >> Dima >> >>
