WARNING: Version 2.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Upgrading
editUpgrading
editBefore upgrading Elasticsearch:
- Consult the breaking changes docs.
- Test upgrades in a dev environment before upgrading your production cluster.
- Always back up your data before upgrading. You cannot roll back to an earlier version unless you have a backup of your data.
Elasticsearch can usually be upgraded using a rolling upgrade process, resulting in no interruption of service. This section details how to perform both rolling upgrades and upgrades with full cluster restarts.
To determine whether a rolling upgrade is supported for your release, please consult this table:
| Upgrade From | Upgrade To | Supported Upgrade Type |
|---|---|---|
|
|
|
|
|
|
|
|
Rolling upgrade (where `y > x `) |
Upgrading Elasticsearch with Plugins
Take plugins into consideration as well when upgrading. Plugins must be upgraded alongside Elasticsearch.
Check with your plugin’s provider to ensure that the plugin is compatible with
your targeted version of Elasticsearch. If doing a rolling upgrade, it may be
worth checking as well that the plugin works across a mixed-version cluster.
Most plugins will have to be upgraded alongside Elasticsearch, although some
plugins accessed primarily through the browser (_site plugins) may continue to
work given that API changes are compatible.
The process for both Rolling upgrade and Full cluster restart is generally as follows, per node.
- Shut down Elasticsearch
- Upgrade Elasticsearch
- Upgrade Plugins
- Start up Elasticsearch