From c405cb7fab6d1f89dc7e29ce6608a311f3483bd7 Mon Sep 17 00:00:00 2001 From: Michel Laterman <82832767+michel-laterman@users.noreply.github.com> Date: Mon, 24 Oct 2022 15:13:46 -0700 Subject: [PATCH] Add agent upgrade retry doc (#2230) * Add agent upgrade retry doc * Fix retry aborting statement * Apply suggestions from code review Co-authored-by: DeDe Morton Co-authored-by: DeDe Morton --- .../ingest-management/fleet/upgrade-elastic-agent.asciidoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc index c0a09ea982..cd412333e4 100644 --- a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc +++ b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc @@ -14,6 +14,11 @@ maintenance window during which the upgrades will occur. If your {stack} subscription level supports it, you can schedule upgrades to occur at a specific date and time. +In most failure cases the {agent} may retry an upgrade after a short wait. The +wait durations between retries are: 1m, 5m, 10m, 15m, 30m, and 1h. During this +time, the {agent} may show up as "retrying" in the {fleet} UI. Note that you +can abort an upgrade that is being retried. See <>. + This approach simplifies the process of keeping your agents up to date. It also saves you time because you don’t need third-party tools or processes to manage upgrades. @@ -87,7 +92,7 @@ image::images/rolling-agent-upgrade.png[Menu for bulk upgrading {agent}s] . Select the amount of time available for the maintenance window. The upgrades are spread out uniformly across this maintenance window to avoid exhausting -network resources. +network resources. + To force selected agents to upgrade immediately when the upgrade is triggered, select **Immediately**. Avoid using this setting for batches of more