From 80203a2f69faa516a58feeea991ccb0a50f4f0ef Mon Sep 17 00:00:00 2001 From: Pius Fung Date: Tue, 12 Aug 2025 09:26:53 -0700 Subject: [PATCH] Update 8.19.1.asciidoc Reverting change based on the [comment](https://github.com/elastic/elasticsearch/pull/132683#discussion_r2268371884). Due to a PR CI issue, the [optimization](https://github.com/elastic/elasticsearch/pull/125403) introduced in 8.19.0 that would have caused the [bug](https://github.com/elastic/elasticsearch/pull/132597) didn't actually get enabled in 8.19.x versions. Therefore, 8.19.0 and 8.19.1 do not have either the optimization or the bug. The optimization will be enabled in 8.19.2 and the bug will be fixed by then. --- docs/reference/release-notes/8.19.1.asciidoc | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/docs/reference/release-notes/8.19.1.asciidoc b/docs/reference/release-notes/8.19.1.asciidoc index f7e0a3aa61b3d..0bff7530ac4d1 100644 --- a/docs/reference/release-notes/8.19.1.asciidoc +++ b/docs/reference/release-notes/8.19.1.asciidoc @@ -144,19 +144,3 @@ This caused unintended timeouts or cancellations during subsequent phases under Engine:: * Available disk space is now recorded when merge tasks are scheduled, helping to diagnose issues caused by running merges despite low disk space on nodes. This information appears in heap dumps and can inform adjustments to `indices.merge.disk.watermark.high` or inspire future enhancements such as aborting already running merges. {es-pull}131711[#131711] - -[discrete] -[[known-issues-8.19.1]] -=== Known issues - -* An [optimization](https://github.com/elastic/elasticsearch/pull/125403) introduced in 8.19.0 contains a [bug](https://github.com/elastic/elasticsearch/pull/132597) that causes merges to fail for shrunk TSDB and LogsDB indices. - - Possible *temporary* workarounds include: - * Configure the ILM policy to not perform force merges after shrinking TSDB or LogsDB indices. - * Add `-Dorg.elasticsearch.index.codec.tsdb.es819.ES819TSDBDocValuesConsumer.enableOptimizedMerge=false` as a Java system property to all data nodes in the cluster and perform a rolling restart. - * *Important:* Remove this property when upgrading to the fixed version to re-enable merge optimization. Otherwise, merges will be slower. - -The bug is addressed in version 8.19.2. - - -