upgrade.asciidoc 3.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  1. [[setup-upgrade]]
  2. = Upgrade {es}
  3. [partintro]
  4. --
  5. {es} can usually be upgraded using a <<rolling-upgrades,Rolling upgrade>>
  6. process so upgrading does not interrupt service. Rolling upgrades are supported:
  7. * Between minor versions
  8. * From 5.6 to 6.8
  9. * From 6.8 to {prev-major-version}
  10. * From {prev-major-version} to {version}
  11. The following table shows the recommended upgrade paths to {version}.
  12. [cols="<1m,3",options="header",]
  13. |====
  14. |Upgrade from
  15. |Recommended upgrade path to {version}
  16. |{prev-major-version}
  17. |<<rolling-upgrades,Rolling upgrade>> to {version}
  18. |7.0–7.3
  19. a|
  20. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  21. . <<rolling-upgrades,Rolling upgrade>> to {version}
  22. |6.8
  23. a|
  24. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  25. . <<rolling-upgrades,Rolling upgrade>> to {version}
  26. |6.0–6.7
  27. a|
  28. . https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
  29. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  30. . <<rolling-upgrades,Rolling upgrade>> to {version}
  31. |====
  32. [WARNING]
  33. ====
  34. The following upgrade paths are *not* supported:
  35. * 6.8 to 7.0.
  36. * 6.7 to 7.1.–{prev-major-version}.
  37. ====
  38. {es} can read indices created in the previous major version. If you
  39. have indices created in 5.x or before, you must reindex or delete them
  40. before upgrading to {version}. {es} nodes will fail to start if
  41. incompatible indices are present. Snapshots of 5.x or earlier indices cannot be
  42. restored to a 7.x cluster even if they were created by a 6.x cluster. For
  43. information about upgrading old indices, see <<reindex-upgrade, Reindex to upgrade>>.
  44. When upgrading to a new version of {es}, you need to upgrade each
  45. of the products in your Elastic Stack. For more information, see the
  46. {stack-ref}/upgrading-elastic-stack.html[Elastic Stack Installation and Upgrade Guide].
  47. To upgrade directly to {version} from 6.6 or earlier, you must shut down the
  48. cluster, install {version}, and restart. For more information, see
  49. <<restart-upgrade, Full cluster restart upgrade>>.
  50. [float]
  51. == Preparing to upgrade
  52. Before upgrading {es}:
  53. . Check the <<deprecation-logging, deprecation log>> to see if you are using
  54. any deprecated features and update your code accordingly. By default,
  55. deprecation warnings are logged when the log level is set to `WARN`.
  56. . Review the <<breaking-changes,breaking changes>> and make any necessary changes
  57. to your code and configuration for {version}.
  58. . If you use custom plugins, make sure compatible versions are available.
  59. . Test upgrades in a dev environment before upgrading your production cluster.
  60. . <<modules-snapshots,Back up your data!>> You must have a snapshot of your
  61. data to roll back to an earlier version.
  62. --
  63. include::upgrade/rolling_upgrade.asciidoc[]
  64. include::upgrade/cluster_restart.asciidoc[]
  65. include::upgrade/reindex_upgrade.asciidoc[]