Elasticsearch version 7.17.12edit

Also see Breaking changes in 7.17.

Known issuesedit

  • High Memory Pressure due to a GC JVM setting change

    This version of Elasticsearch is bundled with JDK 20. In JDK 20 Preventive GC is disabled by default. This may lead to increased memory pressure and an increased number of CircuitBreakerExceptions when retrieving large documents under some load patterns. (issue: #99592)

    If this change affects your use of Elasticsearch, consider re-enabling the previous behaviour by adding the JVM arguments -XX:+UnlockDiagnosticVMOptions -XX:+G1UsePreventiveGC (reference: JDK 20 release notes). It is important to note that this workaround is temporary and works only with JDK 20, which is bundled with Elasticsearch up to version 7.17.13 inclusive. Successive versions are bundling JDK 21+, where this setting has been removed. Specifying those JVM arguments will prevent the JVM (and therefore Elasticsearch Nodes) from starting.

Bug fixesedit

  • Less jank in after-key parsing for unmapped fields #97282 (issue: #85928)
  • Handle failure in TransportUpdateAction#handleUpdateFailureWithRetry #97290 (issue: #97286)
  • Support for Byte and Short as vector tiles features #97619 (issue: #97612)
  • Capture max processors in static init #97119 (issue: #97088)
  • Preserve context in ResultDeduplicator #84038 (issue: #84036)
  • Fix unhandled exception when blobstore repository contains unexpected file #93914


  • Adding null check to fix potential NPE #96785 (issue: #96781)


  • Upgrade Netty to 4.1.94.Final #97114