From 6d31346562da9061d359c8f7b919b32772a740a0 Mon Sep 17 00:00:00 2001 From: Sebastian Bernauer Date: Thu, 5 Oct 2023 16:25:55 +0200 Subject: [PATCH] Update docs/modules/trino/pages/usage-guide/operations/pod-disruptions.adoc Co-authored-by: Malte Sander --- .../trino/pages/usage-guide/operations/pod-disruptions.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/trino/pages/usage-guide/operations/pod-disruptions.adoc b/docs/modules/trino/pages/usage-guide/operations/pod-disruptions.adoc index cd7291b9..5e16c489 100644 --- a/docs/modules/trino/pages/usage-guide/operations/pod-disruptions.adoc +++ b/docs/modules/trino/pages/usage-guide/operations/pod-disruptions.adoc @@ -48,7 +48,7 @@ This results e.g. in the following numbers: == Reduce rolling redeployment durations The default PDBs we write out are pessimistic and will cause the rolling redeployment to take a considerable amount of time. -As an example, when you have 100 workers, we can only take 10 workers down at a time. Assuming a worker takes 5 minutes to properly restart, the whole re-deployment would take (100 nodes / 10 nodes simultaneous * 5 minutest = ) 50 minutes. +As an example, in a cluster with 100 workers, 10 workers are restarted at the same time. Assuming a worker takes 5 minutes to properly restart, the whole redeployment will take (100 nodes / 10 nodes simultaneous * 5 minutest = ) 50 minutes. You can use the following measures to speed this up: