From b0ecbb1ec223bf162eb88a68fef57d5d22476da8 Mon Sep 17 00:00:00 2001 From: Andriy Redko Date: Fri, 19 Apr 2024 11:54:43 -0400 Subject: [PATCH] [BUG] Cannot restore ES 6.x index into OpenSearch 2.x but the migration doc says it should work (#6973) * [BUG] Cannot restore ES 6.x index into OpenSearch 2.x but the migration doc says it should work Signed-off-by: Andriy Redko * Update _upgrade-to/snapshot-migrate.md Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> Signed-off-by: Andriy Redko --------- Signed-off-by: Andriy Redko Signed-off-by: Andriy Redko Co-authored-by: Naarcha-AWS <97990722+Naarcha-AWS@users.noreply.github.com> --- _upgrade-to/snapshot-migrate.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/_upgrade-to/snapshot-migrate.md b/_upgrade-to/snapshot-migrate.md index 60f3d309dd..59ca58c3bf 100644 --- a/_upgrade-to/snapshot-migrate.md +++ b/_upgrade-to/snapshot-migrate.md @@ -9,3 +9,9 @@ nav_order: 5 One popular approach is to take a [snapshot]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-restore) of your Elasticsearch OSS 6.x or 7.x indexes, [create an OpenSearch cluster]({{site.url}}{{site.baseurl}}/opensearch/install/), restore the snapshot on the new cluster, and point your clients to the new host. The snapshot approach can mean running two clusters in parallel, but lets you validate that the OpenSearch cluster is working in a way that meets your needs prior to modifying the Elasticsearch OSS cluster. + +Elasticsearch OSS version | Snapshot migration path +:--- | :--- +5.x | Upgrade to 5.6, then upgrade to 6.8. Reindex all 5.x indexes, make a snapshot, and restore in OpenSearch 1.x. +6.x | Make a snapshot and restore in OpenSearch 1.x +7.x | Make a snapshot and restore in OpenSearch 1.x or OpenSearch 2.x