Skip to content

Commit 7af6bd1

Browse files
committed
Add a known issue for upgrading from 5.x to 6.3.0 (#31501)
This is due to #31482
1 parent 2c6437b commit 7af6bd1

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/reference/release-notes/6.3.asciidoc

+11
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,17 @@
11
[[release-notes-6.3.0]]
22
== {es} version 6.3.0
33

4+
[float]
5+
=== Known issues
6+
7+
Upgrades from any 5.x version will fail for indexes which are prepared using the <<indices-synced-flush, _synced flush API>>,
8+
or were automatically sync-flushed due to inactivity. If upgrading from those versions, please
9+
wait for 6.3.1 to be released.
10+
11+
Clusters with a Gold or Platinum license that are upgrading to 6.3 will need to explicitly set
12+
`xpack.security.enabled: true` in `elasticsearch.yml` to upgrade successfully.
13+
If this value is not set, the cluster will be unable to form after upgrade.
14+
415
Also see <<breaking-changes-6.3>>.
516

617
[[breaking-6.3.0]]

0 commit comments

Comments
 (0)