upgrade.asciidoc 1.6 KB

123456789101112131415161718192021222324252627282930313233343536
  1. [[setup-upgrade]]
  2. == Upgrading
  3. [IMPORTANT]
  4. ===========================================
  5. Before upgrading Elasticsearch:
  6. * Consult the <<breaking-changes,breaking changes>> docs.
  7. * Test upgrades in a dev environment before upgrading your production cluster.
  8. * Always back up your data before upgrading. You cannot roll back to an earlier
  9. version unless you have a <<backup,backup>> of your data.
  10. ===========================================
  11. Elasticsearch can usually be upgraded using a rolling upgrade process,
  12. resulting in no interruption of service. This section details how to perform
  13. both rolling upgrades and upgrades with full cluster restarts.
  14. To determine whether a rolling upgrade is supported for your release, please
  15. consult this table:
  16. [cols="1<m,1<m,3",options="header",]
  17. |=======================================================================
  18. |Upgrade From |Upgrade To |Supported Upgrade Type
  19. |0.90.x |2.x |<<restart-upgrade,Full cluster restart>>
  20. |1.x |2.x |<<restart-upgrade,Full cluster restart>>
  21. |2.x |2.y |<<rolling-upgrades,Rolling upgrade>> (where `y > x `)
  22. |2.x |3.x |<<restart-upgrade,Full cluster restart>>
  23. |=======================================================================
  24. TIP: Take plugins into consideration as well when upgrading. 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.
  25. include::backup.asciidoc[]
  26. include::rolling_upgrade.asciidoc[]
  27. include::cluster_restart.asciidoc[]