From f8f431afdb1d22d75ee5bcb5cd714e512ffca6f1 Mon Sep 17 00:00:00 2001 From: Dan Hermann Date: Tue, 26 Oct 2021 06:56:36 -0500 Subject: [PATCH 1/2] Document removal of freeze index API --- docs/reference/migration/migrate_8_0/api.asciidoc | 15 +++++++++++++++ .../migration/migrate_8_0/indices.asciidoc | 15 +++++++++++++++ 2 files changed, 30 insertions(+) diff --git a/docs/reference/migration/migrate_8_0/api.asciidoc b/docs/reference/migration/migrate_8_0/api.asciidoc index 2c86e0a45442c..9c3fd43eb1696 100644 --- a/docs/reference/migration/migrate_8_0/api.asciidoc +++ b/docs/reference/migration/migrate_8_0/api.asciidoc @@ -6,6 +6,21 @@ //Installation and Upgrade Guide //tag::notable-breaking-changes[] +.The deprecated freeze index API has been removed. +[%collapsible] +==== +*Details* + +The freeze index API (`POST //_freeze`) was deprecated in 7.14 and +removed in 8.0. +https://www.elastic.co/blog/significantly-decrease-your-elasticsearch-heap-memory-usage[Improvements +in heap memory usage] have eliminated the reason to freeze indices. +Existing frozen indices can still be unfrozen with the +<>. + +*Impact* + +Requests made to the old freeze index API will return an error. +==== + .The cat node API's `local` query parameter has been removed. [%collapsible] ==== diff --git a/docs/reference/migration/migrate_8_0/indices.asciidoc b/docs/reference/migration/migrate_8_0/indices.asciidoc index b04c34e392205..a7602dfe27607 100644 --- a/docs/reference/migration/migrate_8_0/indices.asciidoc +++ b/docs/reference/migration/migrate_8_0/indices.asciidoc @@ -18,6 +18,21 @@ instead for that purpose. Requests made to the old `_upgrade` API will return an error. ==== +.The deprecated freeze index API has been removed. +[%collapsible] +==== +*Details* + +The freeze index API (`POST //_freeze`) was deprecated in 7.14 and +removed in 8.0. +https://www.elastic.co/blog/significantly-decrease-your-elasticsearch-heap-memory-usage[Improvements +in heap memory usage] have eliminated the reason to freeze indices. +Existing frozen indices can still be unfrozen with the +<>. + +*Impact* + +Requests made to the old freeze index API will return an error. +==== + .The force merge API's `max_num_segments` and `only_expunge_deletes` parameters cannot both be specified in the same request. [%collapsible] ==== From 9fa13412f23259e53b498de5e2f7fc6707451ef0 Mon Sep 17 00:00:00 2001 From: Dan Hermann Date: Tue, 26 Oct 2021 14:36:18 -0500 Subject: [PATCH 2/2] review comments --- docs/reference/migration/migrate_8_0/api.asciidoc | 15 --------------- .../migration/migrate_8_0/indices.asciidoc | 9 +++++---- 2 files changed, 5 insertions(+), 19 deletions(-) diff --git a/docs/reference/migration/migrate_8_0/api.asciidoc b/docs/reference/migration/migrate_8_0/api.asciidoc index 9c3fd43eb1696..2c86e0a45442c 100644 --- a/docs/reference/migration/migrate_8_0/api.asciidoc +++ b/docs/reference/migration/migrate_8_0/api.asciidoc @@ -6,21 +6,6 @@ //Installation and Upgrade Guide //tag::notable-breaking-changes[] -.The deprecated freeze index API has been removed. -[%collapsible] -==== -*Details* + -The freeze index API (`POST //_freeze`) was deprecated in 7.14 and -removed in 8.0. -https://www.elastic.co/blog/significantly-decrease-your-elasticsearch-heap-memory-usage[Improvements -in heap memory usage] have eliminated the reason to freeze indices. -Existing frozen indices can still be unfrozen with the -<>. - -*Impact* + -Requests made to the old freeze index API will return an error. -==== - .The cat node API's `local` query parameter has been removed. [%collapsible] ==== diff --git a/docs/reference/migration/migrate_8_0/indices.asciidoc b/docs/reference/migration/migrate_8_0/indices.asciidoc index a7602dfe27607..585233c736708 100644 --- a/docs/reference/migration/migrate_8_0/indices.asciidoc +++ b/docs/reference/migration/migrate_8_0/indices.asciidoc @@ -22,12 +22,13 @@ Requests made to the old `_upgrade` API will return an error. [%collapsible] ==== *Details* + -The freeze index API (`POST //_freeze`) was deprecated in 7.14 and -removed in 8.0. +The freeze index API (`POST //_freeze`) has been removed. https://www.elastic.co/blog/significantly-decrease-your-elasticsearch-heap-memory-usage[Improvements in heap memory usage] have eliminated the reason to freeze indices. -Existing frozen indices can still be unfrozen with the -<>. +You can still unfreeze existing frozen indices using the +{ref}/unfreeze-index-api.html[unfreeze index API]. For some use cases, the +frozen tier may be a suitable replacement for frozen indices. See +{ref}/data-tiers.html[data tiers] for more information. *Impact* + Requests made to the old freeze index API will return an error.