WARNING: Version 6.2 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.

« Installing X-Pack Uninstalling X-Pack »
Elastic Docs ›X-Pack for the Elastic Stack [6.2] ›Setting Up X-Pack

Upgrading X-Pack

edit

Upgrading X-Pack

edit

You must upgrade all of the Elastic Stack products you are using when upgrading to a new major version.

The steps you need to take to upgrade differ depending on which products you are using. Want a list that’s tailored to your stack? Try out our Interactive Upgrade Guide.

If you use X-Pack security and are upgrading directly to 6.2.4 from 5.5 or earlier, you must upgrade the .security index after you restart Elasticsearch. Native realm users will not be able to authenticate until the index is upgraded. For instructions, see Upgrading 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:

  1. Stop any machine learning jobs that are running before starting the upgrade process. See Stopping Machine Learning.
  2. Stop Elasticsearch.

  3. Uninstall X-Pack from Elasticsearch:

    bin/elasticsearch-plugin remove x-pack

  4. If you have not already done so, upgrade Elasticsearch.

    If you use X-Pack monitoring, re-use the data directory when you upgrade Elasticsearch. Monitoring identifies unique Elasticsearch nodes by using the persistent UUID, which is stored in the data directory. For more information about the location of the data directory, see path.data and path.logs.

  5. Install the new version of X-Pack into Elasticsearch.

  6. Restart 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.

  7. Uninstall X-Pack from Kibana:

    bin/kibana-plugin remove x-pack

  8. If you have not already done so, upgrade Kibana.

    If you use X-Pack monitoring, you must re-use the data directory when you upgrade Kibana. Otherwise, the Kibana instance is assigned a new persistent UUID and becomes a new instance in the monitoring data.

  9. Install the new version of X-Pack into Kibana.
  10. Restart Kibana.

  11. Uninstall X-Pack from Logstash:

    bin/logstash-plugin remove x-pack

  12. If you have not already done so, upgrade Logstash.

    If you use X-Pack monitoring, you must re-use the data directory when you upgrade Logstash. Otherwise, the Logstash node is assigned a new persistent UUID and becomes a new node in the monitoring data.

  13. Install the new version of X-Pack into Logstash.
  14. Restart Logstash.
« Installing X-Pack Uninstalling X-Pack »