Skip to content

Elasticsearch to Opensearch Upgrade

0

I performed an in-place upgrade from Elasticsearch 7.10 to OpenSearch 1.3, which completed successfully. However, when attempting to upgrade from OpenSearch 1.3 to OpenSearch 2.19, the eligibility check failed due to a few incompatible indices. According to the documentation, these indices need to be reindexed. I wanted to check whether it is mandatory to reindex the affected indices using the Reindex API, or if there are any managed or automated solutions available to avoid manual intervention during this process.

asked a year ago437 views

2 Answers
0

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:

  1. Migrate the indices to hot storage
  2. Reindex the data using the Reindex API
  3. 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:

answered a year ago

0

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 :

  1. Hot storage indexes: Reindex them directly
  2. 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

AWS
EXPERT

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.