Re: Java 17 and Lucene

Thanks for the note of caution Uwe. > On our Jenkins server running with AMD Ryzen CPU it happens quite often that JDK 16, JDK 17 and JDK 18 hang during tests and stay unkillable (only a hard kill with" kill -9") Scary stuff. I'll try to reproduce the hang first and then try to get the JVM logs.

Re: Java 17 and Lucene

Thank you all for the information, it's very useful. Seems like it's best to hold off on upgrading for now, but great to know that different JDK versions are at least being exercised in CI. I'm wondering, is there a better way to assess the production readiness of a Lucene/JDK combination than jus

Re: Java 17 and Lucene

> I would a bit careful: On our Jenkins server running with AMD Ryzen CPU it > happens quite often that JDK 16, JDK 17 and JDK 18 hang during tests and stay > unkillable (only a hard kill with" kill -9"). Previous Java versions don't > hang. It happens not all the time (about 1/4th of all builds

RE: Java 17 and Lucene

Hi, > > On a side note, the Lucene codebase still uses the deprecated (as of > > JDK17) AccessController > > in the RamUsageEstimator class. > > We suppressed the warning for now (based on recommendations > > > > dev/202106.mbox/%3CJIRA.1336944

RE: Java 17 and Lucene

Hi, > Hey, > > Our team at Amazon Product Search recently ran our internal benchmarks with > JDK 17. > We saw a ~5% increase in throughput and are in the process of > experimenting/enabling it in production. > We also plan to test the new Corretto Generational Shenandoah GC. I would a bit carefu