Elasticsearch version 8.4.3edit

Also see Breaking changes in 8.4.

Known issuesedit

  • When using date range search with format that does not have all date fields (missing month or day) an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day) (issue: #90187)
  • 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)

Bug fixesedit

Infra/Core
  • Fix file permission errors to avoid repeated error save loops on Windows #90271 (issue: #90222)
Ingest Node
  • Prevent serialization errors in the nodes stats API #90319 (issue: #77973)

Regressionsedit

Ranking
  • Ensure cross_fields always uses valid term statistics #90314