When changing the version of an existing cluster, either a major or a minor upgrade is performed. The difference is that a minor upgrade takes you from 6.5.2 to 6.5.3, for example, and requires no downtime as a rolling upgrade is performed. A major upgrade takes you from from 2.3 to 5.0, for example, and requires a full cluster restart as part of 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:
To upgrade to a later Elasticsearch version:
- Log into the Elasticsearch Service Console.
On the Deployments page, select a deployment to upgrade.
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.
- In the Deployment version section, click New versions available.
Select a new version.
If you are performing a major version upgrade, the UI will offer you a link to our migration helper tool that can help you 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 had Kibana enabled, the UI will prompt you to also upgrade Kibana.