- Newest
- Most votes
- Most comments
When upgrading from OpenSearch 1.3 to OpenSearch 2.19, reindexing incompatible indices is indeed mandatory. There is no automated or managed solution provided by AWS OpenSearch Service to handle this reindexing process for you.
For indices created in OpenSearch 1.3, Elasticsearch 7.10, or earlier versions, you must manually reindex them before upgrading to newer versions like OpenSearch 2.19. This is especially important because OpenSearch 3.x (and by extension, 2.x) doesn't support these older indices, regardless of whether they're in hot, UltraWarm, or cold storage.
If your incompatible indices are in UltraWarm or cold storage, you'll need to:
- Migrate the indices to hot storage
- Reindex the data using the Reindex API
- Migrate the indices back to warm or cold storage
Alternatively, if you no longer need these indices, you can simply delete them.
To prevent upgrade issues in the future, consider these best practices:
- Reindex larger shards to keep individual shard sizes under 50 GB
- Use the correct number of shards for your configuration
- Initiate upgrades during periods of low cluster usage
- Test updates on non-production domains first
- Ensure your domain has enough CPU, memory, and disk space for the increased load during an upgrade
Sources
Upgrading Amazon OpenSearch Service domains - Amazon OpenSearch Service
Troubleshoot stuck or failed upgrades in OpenSearch Service | AWS re:Post
answered a year ago
When upgrading to OpenSearch 2.3 and later versions (including 2.19), any indexes originally created in Elasticsearch 6.8 or earlier are incompatible with the target version. The upgrade eligibility check will fail if these incompatible indexes exist in your domain, whether they're in hot, UltraWarm, or cold storage .
You must manually reindex the affected indices using the Reindex API. For incompatible indexes in different storage tiers :
- Hot storage indexes: Reindex them directly
- UltraWarm or cold storage indexes:
- Migrate them to hot storage first
- Reindex the data
- Migrate them back to warm or cold storage
Alternatively, you can delete the indexes if you no longer need them .
If you accidentally upgrade to version 2.3 or later without reindexing incompatible indexes first, you won't be able to migrate those indexes out of their current storage tier. Your only option at that point would be to delete them .
Documentation link: https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html
Relevant content
asked 5 years ago
asked 3 years ago
- AWS OFFICIALUpdated 2 months ago
