This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Capturing diagnostics Archived settings »
Elastic Docs ›Elasticsearch Guide [8.16]

Upgrade Elasticsearch

edit

Upgrade Elasticsearch

edit

This documentation is for Elasticsearch 8.16.0, which is not yet released. You can upgrade from a previously released version to a pre-release build, if following a supported upgrade path. Upgrading from a pre-release build to any other build is not supported, and can result in errors or silent data loss. If you run a pre-release build for testing, discard the contents of the cluster before upgrading to another build of Elasticsearch.

Elasticsearch clusters can usually be upgraded one node at a time so upgrading does not interrupt service. For upgrade instructions, refer to Upgrading to Elastic 8.16.0.

Upgrade from 7.x

To upgrade to 8.16.0 from 7.16 or an earlier version, you must first upgrade to 7.17, even if you opt to do a full-cluster restart instead of a rolling upgrade. This enables you to use the Upgrade Assistant to identify and resolve issues, reindex indices created before 7.0, and then perform a rolling upgrade. You must resolve all critical issues before proceeding with the upgrade. For instructions, refer to Prepare to upgrade from 7.x.

Index compatibility

edit

Elasticsearch has full query and write support for indices created in the previous major version. If you have indices created in 6.x or earlier, you might use the archive functionality to import them into newer Elasticsearch versions, or you must reindex or delete them before upgrading to 8.16.0. Elasticsearch nodes will fail to start if incompatible indices are present. Snapshots of 6.x or earlier indices can only restored using the archive functionality to a 8.x cluster even if they were created by a 7.x cluster. The Upgrade Assistant in 7.17 identifies any indices that need to be reindexed or removed.

REST API compatibility

edit

REST API compatibility is a per-request opt-in feature that can help REST clients mitigate non-compatible (breaking) changes to the REST API.

FIPS Compliance and Java 17

edit

Elasticsearch 8.0+ requires Java 17 or later. Elasticsearch 8.13+ has been tested with Bouncy Castle's Java 17 certified FIPS implementation and is the recommended Java security provider when running Elasticsearch in FIPS 140-2 mode. Note - Elasticsearch does not ship with a FIPS certified security provider and requires explicit installation and configuration.

Alternatively, consider using Elasticsearch Service in the FedRAMP-certified GovCloud region.

« Capturing diagnostics Archived settings »