-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Meta] Enable multi-hop migration of data through snapshot-restore #23
Comments
Enabling a legacy snapshot to restore on latest version of OpenSearch would enable users to migrate directly from previous versions of Elasticsearch and OpenSearch to the latest tip via the familiar Snapshot Restore process. I like the idea of solving 1 & 3 tasks first w.r.t. ES 6.x+ versions and later moving to expand this support with subtask 2 to more legacy versions. @kartg |
While snapshot restore is great option for lift-and-shift migrations, it would be exciting to see this functionality expanded to in-place upgrades as well as it provides zero downtime option for version migrations. Could we also track that as part of Multi-version meta issue? |
Related - opensearch-project/OpenSearch#5443 |
Ownership of the extended compatibility of searchable snapshots has been moved to the core We will revisit reindexing of snapshots at a later time. Closing the issue. |
This meta issue tracks feature work that enables customers to migrate their data from a cluster running on a legacy version to the latest version of OpenSearch, through the snapshot-restore mechanism.
Expand the above functionality to support even older versions (say ES 5.0)Investigate re-indexing of old snapshots on the updated clusterThis method could also be used for upgrading clusters in-place, but would result in downtime
The text was updated successfully, but these errors were encountered: