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

Improve rolling upgrade order docs #2576

Merged
merged 2 commits into from
Oct 19, 2023
Merged

Improve rolling upgrade order docs #2576

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc1db52
Improve rolling upgrade order docs
DaveCTurner Oct 19, 2023
ee405ec
Fix line break & add _none
DaveCTurner Oct 19, 2023
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
24 changes: 14 additions & 10 deletions docs/en/install-upgrade/upgrading-elasticsearch.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,16 +22,20 @@ running the older version.
Before you start, <<upgrading-elastic-stack,take the upgrade preparation
steps>>. When performing a <<rolling-upgrades, rolling upgrade>>:

. Upgrade nodes that are **NOT** {ref}/modules-node.html#master-node[master-eligible] first.
You can retrieve a list of these nodes with `GET /_nodes/_all,master:false/_none` or by finding all the nodes configured with `node.master: false`.

. Upgrade nodes tier-by-tier, starting with the frozen tier.
Complete the upgrade for all nodes in each data tier before moving to the next.
Upgrade the frozen tier, then the cold tier, then the warm tier, and upgrade the hot tier last. This ensures {ilm-init} can continue to move data through the tiers during the upgrade. You can get the list of nodes in a specific tier with a `GET /_nodes` request,
for example: `GET /_nodes/data_frozen:true/_none`.

. Upgrade the master-eligible nodes last. You can retrieve a list
of these nodes with `GET /_nodes/master:true`.
. Upgrade the data nodes first, tier-by-tier, starting with the frozen tier,
then the cold tier, then the warm tier, then the hot tier, and finally any other
data nodes which are not in a tier. Complete the upgrade for all nodes in each
data tier before moving to the next. This ensures {ilm-init} can continue to
move data through the tiers during the upgrade. You can get the list of nodes in
a specific tier with a `GET /_nodes` request, for example:
`GET /_nodes/data_frozen:true/_none`.

. Upgrade all remaining nodes that are neither master-eligible nor data nodes.
This includes dedicated ML nodes, dedicated ingest nodes, and dedicated
coordinating nodes.

. Upgrade the master-eligible nodes last. You can retrieve a list of these nodes
with `GET /_nodes/master:true/_none`.

This order ensures that all nodes can join the cluster during the upgrade.
Upgraded nodes can join a cluster with an older master, but older nodes cannot
Expand Down