WARNING: Version 6.0 of the Elastic Stack 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.
You must upgrade all of the Elastic Stack products you are using when upgrading to a new major version.
If you use X-Pack security and are upgrading directly to
6.0.1 from 5.5 or earlier, you must upgrade the
after you restart Elasticsearch. Native realm users will not be able to
authenticate until the index is upgraded. For instructions, see
internal indices. You also need to upgrade the
.security index if
you restore a pre-5.6 snapshot to a fresh 6.0 install.
To upgrade X-Pack:
- Stop any machine learning jobs that are running before starting the upgrade process. See Stopping Machine Learning.
- Stop Elasticsearch.
Uninstall X-Pack from Elasticsearch:
bin/elasticsearch-plugin remove x-pack
- If you have not already done so, upgrade Elasticsearch.
- Install the new version of X-Pack into Elasticsearch.
If you’re upgrading a production cluster, perform a rolling upgrade to ensure recovery is as quick as possible. Rolling upgrades are supported when upgrading to a new minor version. A full cluster restart is required when upgrading to a new major version.
If you encrypt sensitive data in Watcher, there is a breaking change related
system_keyfile. You must use the secure settings keystore and add the contents of the
system_keyon each node in the cluster. See Encrypting Sensitive Data in Watcher.
Uninstall X-Pack from Kibana:
bin/kibana-plugin remove x-pack
- If you have not already done so, upgrade Kibana.
- Install the new version of X-Pack into Kibana.
- Restart Kibana.
Uninstall X-Pack from Logstash:
bin/logstash-plugin remove x-pack
- If you have not already done so, upgrade Logstash.
- Install the new version of X-Pack into Logstash.
- Restart Logstash.