Skip to content

Commit 4ffdf8a

Browse files
renshukieedugonshainaraskas
authored
Clarifications on 'no downtime' during upgrades (#1421)
Current wording suggests that no downtime is expected during upgrades whatever the deployment topology is. Non-HA deployments (on single AZ) are subject to downtime as the Elasticsearch node upgrade happens inline with a rolling change. Also for Kibana upgrade, all Kibana instances are shutdown simultaneously which makes Kibana inaccessible during the Kibana upgrade plan whatever the zone distribution is. Preview here: - [Availability during upgrades](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1421/deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech) --------- Co-authored-by: Edu González de la Herrán <[email protected]> Co-authored-by: shainaraskas <[email protected]>
1 parent e6ca4bb commit 4ffdf8a

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

deploy-manage/upgrade/deployment-or-cluster/upgrade-on-ech.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,22 @@ products:
1616

1717
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.
1818

19-
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.
19+
{{ecloud}} only supports upgrades to released versions. Release candidate builds and master snapshots are not supported.
2020

2121
::::{important}
2222
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.
2323
::::
2424

25+
## Availability during upgrades
26+
27+
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.
28+
29+
When {{kib}} instances are upgraded, all instances are shut down simultaneously, making {{kib}} temporarily inaccessible, even if it's deployed across multiple zones.
30+
31+
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.
32+
33+
Refer to [Plan for production](/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md) for more information about High Availability (HA) on ECH.
34+
2535
## Perform the upgrade [perform-cloud-upgrade]
2636

2737
Log in to your {{ecloud}} environment:

0 commit comments

Comments
 (0)