upgrade.asciidoc 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110
  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. ifeval::[ "{bare_version}" != "{minor-version}.0" ]
  12. * From any version since {minor-version}.0 to {version}
  13. endif::[]
  14. [TIP]
  15. ====
  16. For rolling upgrades between major versions (e.g., 5.6 to 6.8), we recommend
  17. using the {kibana-ref}/upgrade-assistant.html[Kibana Upgrade Assistant].
  18. The upgrade assistant identifies deprecated settings in your cluster and guides
  19. you through the process of resolving issues, including reindexing.
  20. We also recommend checking your <<deprecation-logging,deprecation logs>> for any
  21. other functionality that may have changed.
  22. ====
  23. The following table shows the recommended upgrade paths to {version}.
  24. [cols="<1,3",options="header",]
  25. |====
  26. |Upgrade from
  27. |Recommended upgrade path to {version}
  28. ifeval::[ "{bare_version}" != "{minor-version}.0" ]
  29. |A previous {minor-version} version (e.g., {minor-version}.0)
  30. |<<rolling-upgrades,Rolling upgrade>> to {version}
  31. endif::[]
  32. |{prev-major-version}
  33. |<<rolling-upgrades,Rolling upgrade>> to {version}
  34. |7.0–7.15
  35. a|
  36. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  37. . <<rolling-upgrades,Rolling upgrade>> to {version}
  38. |6.8
  39. a|
  40. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  41. . <<rolling-upgrades,Rolling upgrade>> to {version}
  42. |6.0–6.7
  43. a|
  44. . https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
  45. . https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
  46. . <<rolling-upgrades,Rolling upgrade>> to {version}
  47. |====
  48. [WARNING]
  49. ====
  50. The upgrade path from 6.8 to 7.0 is *not* supported (both full cluster restart and rolling upgrade).
  51. ====
  52. To upgrade directly to {version} from 6.7 or earlier, you must shut down the
  53. cluster, install {version}, and restart. For more information, see
  54. <<restart-upgrade, Full cluster restart upgrade>>.
  55. [WARNING]
  56. ====
  57. In-place downgrades to earlier versions are *not* supported. To downgrade to an
  58. earlier version, <<snapshots-restore-snapshot,restore a snapshot>> taken prior
  59. to the version upgrade.
  60. ====
  61. {es} can read indices created in the previous major version. If you
  62. have indices created in 5.x or before, you must reindex or delete them
  63. before upgrading to {version}. {es} nodes will fail to start if
  64. incompatible indices are present. Snapshots of 5.x or earlier indices cannot be
  65. restored to a 7.x cluster even if they were created by a 6.x cluster. For
  66. information about upgrading old indices, see <<reindex-upgrade, Reindex to upgrade>>.
  67. When upgrading to a new version of {es}, you need to upgrade each
  68. of the products in your Elastic Stack. For more information, see the
  69. {stack-ref}/upgrading-elastic-stack.html[Elastic Stack Installation and Upgrade Guide].
  70. ifeval::["{release-state}"!="released"]
  71. [[upgrade-pre-release]]
  72. NOTE: This documentation is for {es} version {version}, which is not yet
  73. released. You may run a pre-release build of {es} for testing, and you may
  74. upgrade from an earlier released version to a pre-release build of {es}
  75. {version} if permitted by the compatibility table above, but upgrading from a
  76. pre-release build to another build (whether released or not) is unsupported.
  77. Upgrading a pre-release build may result in errors or may appear to succeed
  78. having silently lost some data. You should discard the contents of a cluster
  79. running a pre-release build before using a different build.
  80. endif::[]
  81. --
  82. include::upgrade/rolling_upgrade.asciidoc[]
  83. include::upgrade/cluster_restart.asciidoc[]
  84. include::upgrade/reindex_upgrade.asciidoc[]
  85. include::upgrade/archived-settings.asciidoc[]