Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a known issue for upgrading from 5.x to 6.3.0 #31501

Merged
merged 3 commits into from
Jun 21, 2018
Merged

Add a known issue for upgrading from 5.x to 6.3.0 #31501

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a11bc5b
Update 6.3.asciidoc
bleskes Jun 21, 2018
08eedea
tweak
bleskes Jun 21, 2018
f93de4e
feedback
bleskes Jun 21, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/reference/release-notes/6.3.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,13 @@
[float]
=== Known issues

Upgrades from any 5.x version will fail for indexes which are prepared using the <<indices-synced-flush, _synced flush API>>, or were automatically synced flushed due to inactivity. If upgrading from those version, please wait for 6.3.1 to be released.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

synced flushed -> sync-flushed
from those versionS


Clusters with a Gold or Platinum license that are upgrading to 6.3 will need to explicitly set
`xpack.security.enabled: true` in `elasticsearch.yml` to upgrade successfully.
If this value is not set, the cluster will be unable to form after upgrade.


Also see <<breaking-changes-6.3>>.

[[breaking-6.3.0]]
Expand Down