Skip to content

Clarifications on 'no downtime' during upgrades #1421

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
merged 6 commits into from
May 30, 2025
Merged

Clarifications on 'no downtime' during upgrades #1421

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
45c3de2
Update upgrade-on-ech.md
renshuki May 16, 2025
949b1bc
Apply suggestions from code review
eedugon May 29, 2025
af49cd6
Merge remote-tracking branch 'origin/main' into renshuki-ech-uprade-doc
eedugon May 29, 2025
a29e0fd
availability during upgrades section added
eedugon May 29, 2025
f8727c2
Update deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md
eedugon May 30, 2025
d7bd154
Merge branch 'main' into renshuki-ech-uprade-doc
eedugon May 30, 2025
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
12 changes: 11 additions & 1 deletion deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,12 +16,22 @@ products:

Once you are [prepared to upgrade](/deploy-manage/upgrade/prepare-to-upgrade.md), a single click in the {{ecloud}} console can upgrade a deployment to a newer version, add more processing capacity, change plugins, and enable or disable high availability, all at the same time. During the upgrade process, {{es}}, {{kib}}, Elastic APM, and all of your deployment components are upgraded simultaneously.

You can perform minor version upgrades, upgrades from 8.18 to 9.0.0, and cluster configuration changes with no downtime. {{ecloud}} only supports upgrades to released versions. Release candidate builds and master snapshots are not supported.
{{ecloud}} only supports upgrades to released versions. Release candidate builds and master snapshots are not supported.

::::{important}
Although it’s simple to upgrade an {{ecloud}} deployment, the new version might include breaking changes that affect your application. Ensure you review breaking changes and deprecation logs, make any necessary changes, and test against the new version before upgrading your production deployment.
::::

## Availability during upgrades

For deployments with nodes in more than one availability zone, you can perform minor version upgrades, upgrades from 8.18 to 9.0.0, and cluster configuration changes with no downtime. Deployments with nodes in only one zone might experience downtime during these operations.

When {{kib}} instances are upgraded, all instances are shut down simultaneously, making {{kib}} temporarily inaccessible, even if it's deployed across multiple zones.

If your indices are not highly available (configured with at least one replica), or if certain components of your deployment run in only one zone, you might experience availability issues for requests that depend on that specific data or component, while the affected nodes are being restarted.

Refer to [Plan for production](/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md) for more information about High Availability (HA) on ECH.

## Perform the upgrade [perform-cloud-upgrade]

Log in to your {{ecloud}} environment:
Expand Down
Loading