Evaluate Early Access builds of JDK 22.0.2

[ChrisHegarty]

This issue is intended to help track the evaluation of JDK 22.0.2 Early Access builds, in order to:

• Confirm that the G1 Hotspot JVM bug has been resolved, see
  JDK G1 bug crashes with references [in]to jdk.internal.vm.FillerArray, when upgrading to 8.13.0 or 8.13.1 #106987
• Ensure that Elasticsearch is stable on this yet-to-be-released JDK 22 update.
• Evaluate the workaround by setting, Workaround G1 bug for JDK 22 and 22.0.1 #108571
  -XX:+UnlockDiagnosticVMOptions -XX:G1NumCollectionsKeepPinned=10000000

The motivation for this work is to enable Elasticsearch to bundle the JDK 22.0.2 when it is released ( expected 2024-07-16, see https://www.java.com/releases/ )

relates #106987

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[ChrisHegarty]

The G1 issue is reproducible on Linux x64 with the nyc_taxis benchmark, see https://github.com/elastic/elasticsearch-benchmarks/issues/1989.

We're currently running this benchmark with a locally built JDK 22.0.2 that includes the JDK bug fix https://bugs.openjdk.org/browse/JDK-8329528. The benchmark is run over and over in a loop, just evaluating that Elasticsearch does not crash. So far, it passes successfully. This issue will be updated with more specifics when they are available.

[elasticsearchmachine]

Pinging @elastic/es-perf (Team:Performance)

[gareth-ellis]

We've run about 40 iterations so far of the benchmark, even lowering the heap further, however the issue has not reoccurred.

Update 30/4 - 67 iterations and still going

[ChrisHegarty]

The next step is to evaluate JDK 22.0.1 with the "JVM options" workaround. That is with:

-XX:+UnlockDiagnosticVMOptions -XX:G1NumCollectionsKeepPinned=10000000