IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Elasticsearch version 8.4.1
editElasticsearch version 8.4.1
editAlso see Breaking changes in 8.4.
Known issues
edit- 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.jsonfile to configure Elasticsearch may encounter deadlocks during master elections (issue: #92812)To resolve the deadlock, remove the
settings.jsonfile 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)