From ad229a509fa93077eeb678915d1e67939174157c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 4 Jun 2025 13:57:15 +0200 Subject: [PATCH 1/2] Update prepare-to-upgrade.md Adding a small recommendation that we have always shared for major upgrades. If the user is already on the latest minor (8.18.x) it's also recommended to upgrade to 8.18.latest before upgrading to 9.x, as there could be fixes and improvements on upgrade assistant and other components. A clear example of this could be https://github.com/elastic/stack-docs/pull/3024 --- deploy-manage/upgrade/prepare-to-upgrade.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy-manage/upgrade/prepare-to-upgrade.md b/deploy-manage/upgrade/prepare-to-upgrade.md index 8b4bcb633c..c6d9127bf5 100644 --- a/deploy-manage/upgrade/prepare-to-upgrade.md +++ b/deploy-manage/upgrade/prepare-to-upgrade.md @@ -19,7 +19,9 @@ Upgrading from a release candidate build, such as 9.0.0-rc1, is unsupported. Use To upgrade from 8.17.0 or earlier to 9.0.0, you must first upgrade to the latest 8.18 patch release. This allows you to use the [Upgrade Assistant](prepare-to-upgrade/upgrade-assistant.md) to identify and resolve issues, reindex indices created before 8.0.0, and perform a rolling upgrade. Upgrading to the latest 8.18 patch release is required even if you choose a full {{es}} cluster restart. If you're using 7.x and earlier, you may need to complete multiple upgrades or perform a full-cluster restart to reach the latest 8.18 patch release before upgrading to 9.0.0. -Alternatively, you can create a 9.0.0 deployment and reindex from remote. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade). +If you are already running an 8.18.x version, it's also recommended to upgrade to the latest 8.18 patch release before upgrading to 9.x, as that will ensure the latest version of the upgrade assistant will be used, together with other possible bug fixes that could have implications in the upgrade. + +Alternatively to upgrading the cluster, you can create a 9.0.0 deployment and reindex from remote. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade). :::{note} For flexible upgrade scheduling, 8.18.0 {{beats}} and {{ls}} are compatible with 9.x {{es}}. From 234a3e3fae2af6e38ad280ee38deff0eb63ddb3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 4 Jun 2025 17:09:30 +0200 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- deploy-manage/upgrade/prepare-to-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/upgrade/prepare-to-upgrade.md b/deploy-manage/upgrade/prepare-to-upgrade.md index c6d9127bf5..f9e547fac3 100644 --- a/deploy-manage/upgrade/prepare-to-upgrade.md +++ b/deploy-manage/upgrade/prepare-to-upgrade.md @@ -19,9 +19,9 @@ Upgrading from a release candidate build, such as 9.0.0-rc1, is unsupported. Use To upgrade from 8.17.0 or earlier to 9.0.0, you must first upgrade to the latest 8.18 patch release. This allows you to use the [Upgrade Assistant](prepare-to-upgrade/upgrade-assistant.md) to identify and resolve issues, reindex indices created before 8.0.0, and perform a rolling upgrade. Upgrading to the latest 8.18 patch release is required even if you choose a full {{es}} cluster restart. If you're using 7.x and earlier, you may need to complete multiple upgrades or perform a full-cluster restart to reach the latest 8.18 patch release before upgrading to 9.0.0. -If you are already running an 8.18.x version, it's also recommended to upgrade to the latest 8.18 patch release before upgrading to 9.x, as that will ensure the latest version of the upgrade assistant will be used, together with other possible bug fixes that could have implications in the upgrade. +If you are already running an 8.18.x version, it's also recommended to upgrade to the latest 8.18 patch release before upgrading to 9.x. This ensures that the latest version of the upgrade assistant is used, and any bug fixes that could have implications for the upgrade are applied. -Alternatively to upgrading the cluster, you can create a 9.0.0 deployment and reindex from remote. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade). +As an alternative to upgrading the cluster, you can create a new 9.0.0 deployment and reindex from the original cluster. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade). :::{note} For flexible upgrade scheduling, 8.18.0 {{beats}} and {{ls}} are compatible with 9.x {{es}}.