Elasticsearch version 8.4.2

Elasticsearch version 8.4.2

Also see Breaking changes in 8.4.

Known issues

  • This version contains a regression in multi_match queries that use the cross_fields scoring type. Elasticsearch

    When running a multi_match query with the cross_fields type, Elasticsearch can sometimes throw an IllegalArgument exception with the message “totalTermFreq must be at least docFreq”. If you use the cross_fields scoring type, it is recommended that you skip version 8.4.2. This regression was fixed in version 8.4.3.

  • 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)

  • 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 fixes

Allocation

  • Fix debug mode in MaxRetryAllocationDecider #89973

Authentication

  • Fix double sending of response in TransportOpenIdConnectPrepareAuthenticationAction #89930

Autoscaling

  • Fix issue with autoscaling after a clone or split #89768 (issue: #89758)

Health

  • Fix the conditions for fetching remote master history #89472 (issue: #89431)

ILM+SLM

Infra/Core

  • Extend the date rounding logic to be conditional #89693 (issues: #89096, #58986)
  • Fix FileSettingsService hang on error update #89630
  • Implement fix to terminate file Watcher thread to avoid deadlock #89934

Ingest Node

  • Fix pipeline id not present in ingest metadata inside on_failure block #89632

Machine Learning

  • Fix memory leak in TransportDeleteExpiredDataAction #89935
  • Do not retain categorization tokens when existing category matches #2398

Network

  • Fix memory leak when double invoking RestChannel.sendResponse #89873

Ranking

  • Avoid negative scores with cross_fields type #89016 (issue: #44700)

Rollup

  • Fork TransportRollupCapsAction to MANAGEMENT POOL #89803

Search

  • Empty intervals needs to start in position -1 #89962 (issue: #89789)

Transform

Enhancements

Allocation

  • Log unsuccessful attempts to get credentials from web identity tokens #88241

Health

  • Add delayed allocation diagnosis case to shards availability indicator #89056

Upgrades

Packaging