Skip to content

Clarify rolling-upgrade docs #47279

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

Merged
DaveCTurner merged 3 commits into from
Sep 30, 2019
Merged

Clarify rolling-upgrade docs #47279

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
18fa77b
Clarify rolling-upgrade docs
DaveCTurner Sep 30, 2019
22943e8
Apply suggestions from code review
DaveCTurner Sep 30, 2019
ff96ab0
Reformat
DaveCTurner Sep 30, 2019
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
11 changes: 11 additions & 0 deletions docs/reference/upgrade/rolling_upgrade.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ a time so upgrading does not interrupt service. Running multiple versions of
not supported, as shards cannot be replicated from upgraded nodes to nodes
running the older version.

It is best to upgrade the master-ineligible nodes in your cluster first and then
upgrade the master-eligible nodes. Once enough of the master-eligible nodes have
been upgraded they may form a cluster that nodes of older versions cannot join.
If you upgrade the master-eligible nodes last then all the other nodes will not
be running an older version and so they will be able to join the cluster.

Rolling upgrades are supported:

* Between minor versions
Expand Down Expand Up @@ -53,6 +59,11 @@ include::shut-down-node.asciidoc[]
--
include::upgrade-node.asciidoc[]
include::set-paths-tip.asciidoc[]

[[rolling-upgrades-bootstrapping]]
NOTE: You should leave `cluster.initial_master_nodes` unset while performing a
rolling upgrade. Each upgraded node is joining an existing cluster so there is
no need for <<modules-discovery-bootstrap-cluster,cluster bootstrapping>>.
--

. *Upgrade any plugins.*
Expand Down