A newer version is available. For the latest information, see the current release documentation.
« Full cluster restart upgrade Reindex in place »
Elastic Docs ›Elasticsearch Guide [7.17] ›Upgrade Elasticsearch

Reindex before upgrading

edit

Reindex before upgrading

edit

Elasticsearch can read indices created in the previous major version. If you have indices created in 5.x or before, you must reindex or delete them before upgrading to 7.17.26. Elasticsearch nodes will fail to start if incompatible indices are present. Snapshots of 5.x or earlier indices cannot be restored to a 7.x cluster even if they were created by a 6.x cluster. Any index created in 6.x is compatible with 7.x and does not require a reindex.

This restriction also applies to the internal indices that are used by Kibana and the X-Pack features. Therefore, before you can use Kibana and X-Pack features in 7.17.26, you must ensure the internal indices have a compatible index structure.

You have two options for reindexing old indices:

  • Reindex in place on your 6.x cluster before upgrading.
  • Create a new 7.17.26 cluster and Reindex from remote. This enables you to reindex indices that reside on clusters running any version of Elasticsearch.

Upgrading time-based indices

If you use time-based indices, you likely won’t need to carry pre-6.x indices forward to 7.17.26. Data in time-based indices generally becomes less useful as time passes and are deleted as they age past your retention period.

Unless you have an unusually long retention period, you can just wait to upgrade to 6.x until all of your pre-6.x indices have been deleted.

« Full cluster restart upgrade Reindex in place »