When upgrading the version of an existing cluster, either a minor or major upgrade is performed. The difference is that a minor upgrade takes you from 6.8.2 to 6.8.3, while a major upgrade takes you from 6.8 to 7.10.
If you are upgrading to version 6.7 and later, minor or major upgrades to highly available deployments require little to no downtime as a rolling upgrade is performed.
Major version upgrades sometimes require other changes due to breaking changes or discontinued features. For example, some special considerations apply when upgrading to Elasticsearch 5.0. Our recommended approach for major version upgrades is to create a new deployment with the latest major version you want to upgrade to, reindex everything and make sure index requests are temporarily sent to both clusters. With the new cluster ready, tested, and working, you can then remove the old deployment.
If you are upgrading to version 6.6 and earlier, major upgrades require a full cluster restart to complete the upgrade process.
Patch releases also require no downtime when upgrading highly available deployments. A patch fix release takes you from 5.5.1 to 5.5.3, for example.
Before you beginedit
When upgrading from one recent major Elasticsearch version to the next, we recommend that you prepare ahead of time to make the process go smoothly. To learn more, see:
Perform the upgradeedit
To upgrade a cluster in Elastic Cloud Enterprise:
- Log into the Cloud UI.
On the deployments page, select your deployment.
Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
- Click Upgrade.
Select one of the available software versions. Let the user interface guide you through the steps for upgrading a deployment. When you save your changes, your deployment configuration is updated to the new version.
You cannot downgrade after upgrading, so plan ahead to make sure that your applications still work after upgrading. For more information on changes that might affect your applications, see Breaking changes.
- If you are upgrading to version 6.6 and earlier, major upgrades require a full cluster restart to complete the upgrade process.