If you have a cluster and want to upgrade to version 7.x, there are a few things you must do to prepare for the upgrade. Preparing for your upgrade ahead of time ensures that you can enjoy the new features and improved usability of Elasticsearch 7.x as quickly as possible.
Before you beginedit
Elastic Cloud Enterprise upgrades differ from your on-premise installation because all major configuration changes for Elasticsearch, Kibana, and the security features are handled for you.
When you upgrade, Elastic Cloud Enterprise automatically runs the deprecation API to retrieve information about the cluster, node, and index-level settings that need to be removed or changed. If there are any deprecation issues that would prevent the upgraded deployment from successfully performing, the upgrade fails. To resolve the deprecation issues, use the Upgrade Assistant in Kibana. If your cluster does not include a Kibana instance yet, you can enable Kibana first, then use the Upgrade Assistant. After you resolve the deprecation issues, try the upgrade again.
For more information, refer to:
Snapshot behavior during upgradesedit
To keep your data safe, Elastic Cloud Enterprise takes a snapshot before making any changes to your cluster. After a major version upgrade is complete, and the first successful snapshot with the new major version is available, all snapshots taken with the previous version of Elasticsearch are removed.
For example, before upgrading from Elasticsearch version 6.7 to version 7.x, a snapshot is taken. After the upgrade to version 7.x is complete, and a snapshot is available, all snapshots taken with version 6.x are removed.
To enable snapshots, configure the snapshot repository.
Elasticsearch 7.x is compatible with indices created in version 6.0 or later. If you have indices from version 5.x or earlier, you must remove or reindex them before you upgrade.
If prompted by Elastic Cloud Enterprise, use the Upgrade Assistant in Kibana to reindex your data.
Review breaking changesedit
Major version upgrades can include changes that expose the upgrading process to possible risk. A breaking change is the result of a functional change between major Elasticsearch versions, and requires you to perform additional steps to ensure that you can use the new version as intended.
For more information, refer to Breaking changes in 7.0.
Review the known issuesedit
The following known issues apply to the Elastic Stack 7.0.0 release:
- There are deprecated APIs in 7.0.0 that are still available for use. If you see warnings in the logs about the deprecated APIs, you can ignore them.
- Elastic Cloud Enterprise does not support the ability to upgrade to or from release candidate builds, such as 7.0.0-rc1.
- For Elasticsearch 7.8 and later the Snapshot Lifecycle Managment (SLM) api is always enabled. In past Elasticsearch versions Elastic Cloud Enterprise has proactively disabled this feature as it may conflict with automated snapshot functionality built in with Elastic Cloud Enterprise. Elastic Cloud Enterprise 2.5.0 supports integration with SLM and use it for the automated snapshots. When running Elasticsearch 7.8 or later on versions of Elastic Cloud Enterprise older than 2.5.0 then automated snapshots against repositories instrumented by Elastic Cloud Enterprise must only be configured from the ui or api in Elastic Cloud Enterprise and not through Kibana or Elasticsearch.
- For Elasticsearch 7.8 and later the Index Lifecycle Managment (ILM) API is always enabled, even if the cluster is still using the deprecated index curation. If index curation and ILM are both configured to process the same indices the outcome can be unpredictable. As other stack products default to using ILM when it is available in Elasticsearch, we strongly encourage you to migrate to index lifecycle management. It also has a superior feature set.
Log into Kibanaedit
When you upgrade from version 6.7 to 7.0, you must first log into Kibana to make sure that your upgrade is successful.
Update the security realm settingsedit
During the upgrade process, you are prompted to update the security realm settings when your
user_settings include a
There are two settings that prompt you to update:
If the security realm settings are located in
user_settings_override, contact support to help you upgrade.
If the security realm settings are located in
user_settings, you’ll receive a message that allows you modify these settings.
To modify the
- On the Update security realm settings window, edit the settings.
- Click Update settings.
A note about X-Packedit
In Elasticsearch version 7.0 and later, the security features to keep your Elastic Cloud Enterprise deployments safe are now referred to simply as security features instead of X-Pack.
For information about the security features in Elasticsearch version 7.0 and earlier, refer to Secure your clusters.