iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Address Keith's comments, minor improvements

This commit is contained in:
aetter 2021-06-07 13:46:42 -07:00
parent a8887c8340
commit c2deae9d30
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/migrate/docker-migrate.md
View File

@ -7,8 +7,8 @@ nav_order: 25
# Docker migration
If you use Docker Compose, we highly recommend that you perform what amounts to a [cluster restart upgrade](../upgrade-migrate/). Update your cluster configuration with new images, new settings, and new environment variables. Then stop and start the cluster. This process requires downtime, but takes very few steps and lets you continue to treat the cluster as a single entity that you can reliably deploy and redeploy.
If you use a container orchestration system like Kubernetes (or manage your containers manually) and want to avoid downtime, think of the process not as an upgrade of each node, but as a decommissioning and replacement of each node. One by one, add OpenSearch nodes to the cluster and remove Elasticsearch OSS nodes.
If you use Docker Compose, we highly recommend that you perform what amounts to a [cluster restart upgrade](../upgrade-migrate/). Update your cluster configuration with new images, new settings, and new environment variables, and test it. Then stop and start the cluster. This process requires downtime, but takes very few steps and lets you continue to treat the cluster as a single entity that you can reliably deploy and redeploy.
The most important step is to leave your data volumes intact. **Don't** run `docker-compose down -v`.
If you use a container orchestration system like Kubernetes (or manage your containers manually) and want to avoid downtime, think of the process not as an upgrade of each node, but as a decommissioning and replacement of each node. Gradually add OpenSearch nodes to the cluster while removing Elasticsearch OSS nodes.

14
docs/migrate/upgrade-migrate.md
View File

@ -5,9 +5,9 @@ parent: Migrate to OpenSearch
nav_order: 15
---
# Upgrade approach (Linux)
# Upgrade to OpenSearch (Linux)
If you want to upgrade your existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach](../snapshot-migrate/) unappealing, you must first upgrade your Elasticsearch OSS cluster to version 6.x or 7.x.
If you want to migrate an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach](../snapshot-migrate/) unappealing, you can upgrade the cluster instead. The first step is to upgrade your Elasticsearch OSS cluster to version 6.x or 7.x.
Elasticsearch OSS supports two types of upgrades: rolling and cluster restart.
@ -80,11 +80,11 @@ Elasticsearch OSS version | Rolling upgrade path | Cluster restart upgrade path
```bash
# Elasticsearch OSS
curl -XGET 'localhost:9200/_nodes/_all?pretty=true'
# Open Distro for Elasticsearch
# Open Distro for Elasticsearch with security plugin enabled
curl -XGET 'https://localhost:9200/_nodes/_all?pretty=true' -u 'admin:admin' -k
```
Specifically, check the `nodes.node-id.version` portion of the response.
Specifically, check the `nodes.<node-id>.version` portion of the response.
1. (Rolling) Repeat steps 2--5 until all nodes are using the new version.
@ -135,7 +135,7 @@ Elasticsearch OSS version | Rolling upgrade path | Cluster restart upgrade path
1. Set the `OPENSEARCH_PATH_CONF` environment variable to the directory that contains `opensearch.yml` (e.g. `/etc/opensearch`).
1. In `opensearch.yml`, set `path.data` and `path.logs`. If you are migrating from Elasticsearch OSS, you might also want to disable the security plugin for the time being. `opensearch.yml` might look something like this:
1. In `opensearch.yml`, set `path.data` and `path.logs`. You might also want to disable the security plugin for now. `opensearch.yml` might look something like this:
```yml
path.data: /var/lib/opensearch
@ -157,10 +157,10 @@ Elasticsearch OSS version | Rolling upgrade path | Cluster restart upgrade path
# Security plugin disabled
curl -XGET 'localhost:9200/_nodes/_all?pretty=true'
# Security plugin enabled
curl -XGET 'https://localhost:9200/_nodes/_all?pretty=true' -u 'admin:admin' -k
curl -XGET -k -u 'admin:admin' 'https://localhost:9200/_nodes/_all?pretty=true'
```
Specifically, check the `nodes.node-id.version` portion of the response.
Specifically, check the `nodes.<node-id>.version` portion of the response.
1. (Rolling) Repeat steps 2--5 until all nodes are using OpenSearch.