Elasticsearch version 7.17.10
editElasticsearch version 7.17.10
editAlso see Breaking changes in 7.17.
Known issues
edit-
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. -
The deprecated
index.mapper.dynamic
setting can break your cluster. It can only be set using the Update index settings API. Symptoms include nodes failing to start or shards failing to allocate. Do not use this setting in versions prior to 7.17.22. The bug is fixed in 7.17.22. (issue: #109160)
Bug fixes
edit- Allocation
-
-
Skip
DiskThresholdMonitor
when cluster state is not recovered #93699
-
Skip
- CCR
-
- Deduplicate Heavy CCR Repository CS Requests #91398
- ILM+SLM
- Infra/Core
- Infra/REST API
-
- Fixes CORS headers needed by Elastic clients #85791
- Ingest Node
- Search
- Stats
- Transform
-
-
Catch deprecations as
Exception
rather thanIOException
#94553
-
Catch deprecations as