From bf101edfe911bd042dc097da06f95e680f8ca996 Mon Sep 17 00:00:00 2001 From: Sokratis Papadopoulos Date: Wed, 22 Oct 2025 14:57:47 +0200 Subject: [PATCH 1/2] Update v3 rolling upgrade instructions with minimum version requirement Added note about minimum required cluster version for upgrades to 3.x.x. Signed-off-by: Sokratis Papadopoulos --- _migrate-or-upgrade/rolling-upgrade/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/_migrate-or-upgrade/rolling-upgrade/index.md b/_migrate-or-upgrade/rolling-upgrade/index.md index 04660bb2d62..cdd89d90733 100644 --- a/_migrate-or-upgrade/rolling-upgrade/index.md +++ b/_migrate-or-upgrade/rolling-upgrade/index.md @@ -24,6 +24,9 @@ Before making any changes to your OpenSearch cluster, is it highly recommended t **Important**: OpenSearch nodes **cannot be downgraded**. If you need to revert the upgrade, then you will need to perform a new installation of OpenSearch and restore the cluster from a snapshot. Take a snapshot and store it in a remote repository before beginning the upgrade procedure. Rolling upgrades are **only supported between major adjacent versions**, for example, from OpenSearch 1.x to 2.x but not 1.x to 3.x. {: .important} +**Important**: The minimum required cluster version for upgrades to `3.x.x` is `2.19.0`. +{: .important} + ## Performing the upgrade 1. Verify the health of your OpenSearch cluster before you begin. You should resolve any index or shard allocation issues prior to upgrading to ensure that your data is preserved. A status of **green** indicates that all primary and replica shards are allocated. See [Cluster health]({{site.url}}{{site.baseurl}}/api-reference/cluster-api/cluster-health/) for more information. The following command queries the `_cluster/health` API endpoint: From 7fa299b3ebdb9515903e30d61190b0c16b65a9e8 Mon Sep 17 00:00:00 2001 From: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> Date: Tue, 9 Dec 2025 09:02:35 -0500 Subject: [PATCH 2/2] Update _migrate-or-upgrade/rolling-upgrade/index.md Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com> --- _migrate-or-upgrade/rolling-upgrade/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_migrate-or-upgrade/rolling-upgrade/index.md b/_migrate-or-upgrade/rolling-upgrade/index.md index cdd89d90733..5c968faae6b 100644 --- a/_migrate-or-upgrade/rolling-upgrade/index.md +++ b/_migrate-or-upgrade/rolling-upgrade/index.md @@ -24,7 +24,7 @@ Before making any changes to your OpenSearch cluster, is it highly recommended t **Important**: OpenSearch nodes **cannot be downgraded**. If you need to revert the upgrade, then you will need to perform a new installation of OpenSearch and restore the cluster from a snapshot. Take a snapshot and store it in a remote repository before beginning the upgrade procedure. Rolling upgrades are **only supported between major adjacent versions**, for example, from OpenSearch 1.x to 2.x but not 1.x to 3.x. {: .important} -**Important**: The minimum required cluster version for upgrades to `3.x.x` is `2.19.0`. +**Important**: The minimum required cluster version for upgrades to 3.x.x is 2.19.0. {: .important} ## Performing the upgrade