Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ products:

# Upgrade {{es}} [upgrading-elasticsearch]

An {{es}} cluster can be upgraded one node at a time so upgrading does not interrupt service. Running multiple versions of {{es}} in the same cluster beyond the duration of an upgrade is not supported, as shards cannot be replicated from upgraded nodes to nodes running the older version.
This document provides the detailed steps for performing a rolling upgrade of a self-managed {{es}} cluster. A rolling upgrade allows you to upgrade your cluster one node at a time without interrupting service. Running multiple versions of {{es}} in the same cluster beyond the duration of an upgrade is not supported, as shards cannot be replicated from upgraded nodes to nodes running the older version.

:::{note}
Upgrading from a release candidate build, such as 9.0.0-rc1, is unsupported. Use pre-releases only for testing in a temporary environment.
Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/upgrade/plan-upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ The minimum steps your plan should include are:
1. Upgrade {{es}} and {{kib}} to the latest 8.19 version, as a requirement for the major upgrade to {{version.stack}}.
2. Upgrade all ingest components to the latest 8.19 version, as otherwise they won't be compatible with {{es}} running {{version.stack}}.
3. Follow all [preparation steps](./prepare-to-upgrade.md) and use the upgrade assistant to ensure the cluster is ready for a major upgrade.
4. {{es}} and {{kib}} to {{version.stack}}.
4. Upgrade {{es}} and {{kib}} to {{version.stack}}.

## Next steps

Expand Down
Loading