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.5.
If you are upgrading to version 6.7 and later, minor or major upgrades 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. A patch fix release takes you from 5.5.1 to 5.5.3, for example.
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:
If you have a custom plugin installed, you must update the plugin so that it matches the Elasticsearch version that you are upgrading to. When the custom plugin does not match the Elasticsearch version, the upgrade fails.
To successfully replace and override a plugin which is being upgraded, the
name attribute contained in the
plugin-descriptor.properties file must be the exact same as the currently installed plugin’s
name attribute. If the attributes do not match, the new plugin bundle will be added to the cluster as a completely new and separate plugin.
To upgrade a cluster in Elasticsearch Add-On for Heroku:
Log into the Elasticsearch Add-On for Heroku console.
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
- From the Deployments page, select your deployment.
- In the Deployment version section, click New versions available.
Select a new version.
If you perform a major version upgrade, the UI provides a link to our migration helper tool that helps you to determine if a direct upgrade is feasible. You might also want to consider our Best Practices for Major Version Upgrades and our Elastic Stack upgrade guide.
- Optional: Make any other changes that are needed, such as increasing the capacity or adding plugins.
- Click Upgrade deployment. The new configuration takes a few minutes to create.
- If you are upgrading to version 6.6 and earlier, major upgrades require a full cluster restart to complete the upgrade process.
If you had Kibana enabled, the UI will prompt you to also upgrade Kibana. The Kibana upgrade takes place separately from the Elasticsearch version upgrade and needs to be triggered manually:
- On the Deployments page, select your deployment.
- From your deployment menu, select Kibana.
- If the button is available, click Upgrade Kibana. If the button is not available, Kibana does not need to be upgraded further.
- Confirm the upgrade.