Add breaking changes documentation for ES 6.8 to OS 1.x migration issues (#4856)
* fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> * fix#4831 es to os migration issues Signed-off-by: cwillum <cwmmoore@amazon.com> --------- Signed-off-by: cwillum <cwmmoore@amazon.com>
This commit is contained in:
Chris Moore
GitHub
parent
5306134c41
commit
b2d258d513
|
|
@ -8,7 +8,12 @@ nav_order: 15
|
|||
|
||||
If you want to migrate from an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach]({{site.url}}{{site.baseurl}}/upgrade-to/snapshot-migrate/) unappealing, you can migrate your existing nodes from Elasticsearch OSS to OpenSearch.
|
||||
|
||||
If your existing cluster runs an older version of Elasticsearch OSS, the first step is to upgrade to version 6.x or 7.x. Elasticsearch OSS supports two types of upgrades: rolling and cluster restart.
|
||||
If your existing cluster runs an older version of Elasticsearch OSS, the first step is to upgrade to version 6.x or 7.x.
|
||||
|
||||
Before deciding on the version of Elasticsearch OSS for your upgrade, refer to the [Migrating to OpenSearch and limits on the number of nested JSON objects]({{site.url}}{{site.baseurl}}/breaking-changes/#migrating-to-opensearch-and-limits-on-the-number-of-nested-json-objects) documentation in Breaking changes to see whether the issue will have an impact on your cluster and, therefore, your decisions about upgrades and migration.
|
||||
{: .important }
|
||||
|
||||
Elasticsearch OSS supports two types of upgrades: rolling and cluster restart.
|
||||
|
||||
- Rolling upgrades let you shut down one node at a time for minimal disruption of service.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,17 @@ parent: OpenSearch documentation
|
|||
permalink: /breaking-changes/
|
||||
---
|
||||
|
||||
## 1.x
|
||||
|
||||
The following breaking changes are relevant to OpenSearch versions 1.x.
|
||||
|
||||
### Migrating to OpenSearch and limits on the number of nested JSON objects
|
||||
|
||||
Migrating from Elasticsearch OSS version 6.8 to OpenSearch version 1.x will fail when a cluster contains any document that includes more than 10,000 nested JSON objects across all fields. Elasticsearch version 7.0 introduced the `index.mapping.nested_objects.limit` setting to guard against out-of-memory errors and assigned the setting a default of `10000`. OpenSearch adopted this setting at its inception and enforces the limitation on nested JSON objects. However, because the setting is not present in Elasticsearch 6.8 and not recognized by this version, migration to OpenSearch 1.x can result in incompatibility issues that block shard relocation between Elasticsearch 6.8 and OpenSearch versions 1.x when the number of nested JSON objects in any document surpasses the default limit.
|
||||
|
||||
Therefore, we recommend evaluating your data for these limits before attempting to migrate from Elasticsearch 6.8.
|
||||
|
||||
|
||||
## 2.0.0
|
||||
|
||||
### Remove mapping types parameter
|
||||
|
|
|
|||
Loading…
Reference in New Issue