Elasticsearch version 8.13.3

Elasticsearch version 8.13.3

Also see Breaking changes in 8.13.

Breaking changes

SQL

  • Limit how much space some string functions can use #107333

Known issues

  • When upgrading clusters from version 8.11.4 or earlier, if your cluster contains non-master-eligible nodes, information about the new functionality of these upgraded nodes may not be registered properly with the master node. This can lead to some new functionality added since 8.12.0 not being accessible on the upgraded cluster. If your cluster is running on ECK 2.12.1 and above, this may cause problems with finalizing the upgrade. To resolve this issue, perform a rolling restart on the non-master-eligible nodes once all Elasticsearch nodes are upgraded. This issue is fixed in 8.15.0.
  • The pytorch_inference process used to run Machine Learning models can consume large amounts of memory. In environments where the available memory is limited, the OS Out of Memory Killer will kill the pytorch_inference process to reclaim memory. This can cause inference requests to fail. Elasticsearch will automatically restart the pytorch_inference process after it is killed up to four times in 24 hours. (issue: #110530)

Bug fixes

Data streams

  • Avoid unintentionally clearing the DataStream.rolloverOnWrite flag #107122

ES|QL

Indices APIs

  • GET /_all should return hidden indices with visible aliases #106975

Mapping

  • Fix merging component templates with a mix of dotted and nested object mapper definitions #106077 (issue: #105482)

Network

  • Handle exceptions thrown by HTTP header validation #107355 (issue: #107338)

Percolator

  • Percolator named queries: rewrite for matched info #107432 (issue: #107176)

Search

  • Fix minimized_round_trips in lookup runtime fields #107785

Enhancements

ES|QL

  • ESQL: Introduce language versioning to REST API #106824