preparing_to_upgrade.asciidoc 1.1 KB

12345678910111213141516171819202122232425262728
  1. [float]
  2. === Preparing to upgrade
  3. It is important to prepare carefully before starting an upgrade. Once you have
  4. started to upgrade your cluster to version {version} you must complete the
  5. upgrade. As soon as the cluster contains nodes of version {version} it may make
  6. changes to its internal state that cannot be reverted. If you cannot complete
  7. the upgrade then you should discard the partially-upgraded cluster, deploy an
  8. empty cluster of the version before the upgrade, and restore its contents from
  9. a snapshot.
  10. Before you start to upgrade your cluster to version {version} you should do the
  11. following.
  12. . Check the <<deprecation-logging, deprecation log>> to see if you are using any
  13. deprecated features and update your code accordingly.
  14. . Review the <<breaking-changes,breaking changes>> and make any necessary
  15. changes to your code and configuration for version {version}.
  16. . If you use any plugins, make sure there is a version of each plugin that is
  17. compatible with {es} version {version}.
  18. . Test the upgrade in an isolated environment before upgrading your production
  19. cluster.
  20. . <<modules-snapshots,Back up your data by taking a snapshot!>>