mirror of
https://github.com/iSharkFly-Docs/opensearch-docs-cn
synced 2025-03-09 14:38:01 +00:00
* Added snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Snapshot management v2 Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added user roles Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added SME comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Changed dashboards access from index management to snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Editorial comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
1.3 KiB
1.3 KiB
layout | title | nav_order | redirect_from | |
---|---|---|---|---|
default | About the process | 1 |
|
About the process
The process of upgrading from Elasticsearch OSS (including Open Distro for Elasticsearch) to OpenSearch varies depending on your current version of Elasticsearch OSS, install type, tolerance for downtime, and cost-sensitivity. Rather than concrete steps to cover every situation, we have general guidance for the process.
Three approaches exist:
- Use a snapshot to migrate your Elasticsearch OSS data to a new OpenSearch cluster.
- Perform a rolling upgrade or cluster restart upgrade on your existing nodes.
- Replace existing Elasticsearch OSS nodes with new OpenSearch nodes. Node replacement is most popular when upgrading Docker clusters.
Regardless of your approach, to safeguard against data loss, we recommend that you take a snapshot of all indexes prior to any migration.
If your existing clients include a version check, such as recent versions of Logstash OSS and Filebeat OSS, check compatibility before upgrading.