Elasticsearch version 8.5.2edit

Also see Breaking changes in 8.5.

Known issuesedit

  • Machine learning datafeeds cannot be listed if any are not modified since version 6.x

    If you have a datafeed that was created in version 5.x or 6.x and has not been updated since 7.0, it is not possible to list datafeeds in 8.4 and 8.5. This means that anomaly detection jobs cannot be managed using Kibana. This issue is fixed in 8.6.0.

    If you upgrade to 8.4 or 8.5 with such a datafeed, you need to work around the problem by updating each datafeed’s authorization information using these steps.

  • Orchestrators which use a settings.json file to configure Elasticsearch may encounter deadlocks during master elections (issue: #92812)

    To resolve the deadlock, remove the settings.json file and restart the affected node.

  • Parsing a request when the last element in an array is filtered out (for instance using _source_includes) fails. This is due to a bug in Jackson parser. Fixed in Elasticsearch 8.6.1 (#91456)
  • When the ingest attachment processor is used, the interaction of Tika with log4j 2.18.0 and higher (introduced in Elasticsearch 8.4.0) results in excessive logging. This logging is so excessive that it can lead to cluster instability, to the point where the cluster is unusable and nodes must be restarted. (issue: #91964). This issue is fixed in Elasticsearch 8.7.0 (#93878)

    To resolve the issue, upgrade to 8.7.0 or higher.

Bug fixesedit

  • Avoid potential unsupported operation exception in doc bitset cache #91490
  • Refine bwc version checks on EqlSearchRequest #91510
  • SLM uneahlthy policies diagnosis recommends correct URL in action #91506
Ingest Node
  • Refactor DatabaseNodeService as a cluster state listener #91567 (issue: #86999)
  • Fix NPE in IndexService getNodeMappingStats #91334 (issue: #91259)
  • Fix failure when resolving indices from CCS #91622 (issue: #91550)


  • Remove version limitations for CCS #91409
Ingest Node
  • Refactor enrich maintenance coordination logic #90931