From 57482ba9618b64b831f6c894e80a0a8b09429d2b Mon Sep 17 00:00:00 2001 From: michel-laterman Date: Thu, 6 Oct 2022 12:13:17 -0700 Subject: [PATCH 1/3] Add agent upgrade retry doc --- .../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..bc4345f7ee 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 betweem retries are: 1m, 5m, 10m, 15m, 30m, 1h. During this +time, the {agent} may show up as "retrying" in the {fleet} UI. Note that an +{agent} that is being retried, the upgrade may be aborted as detailed below. + 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 From 8b92371d5c5434d1f299e21a93abf1384362bf9f Mon Sep 17 00:00:00 2001 From: michel-laterman Date: Thu, 6 Oct 2022 12:17:30 -0700 Subject: [PATCH 2/3] Fix retry aborting statement --- docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 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 bc4345f7ee..b679554a1e 100644 --- a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc +++ b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc @@ -17,7 +17,7 @@ date and time. In most failure cases the {agent} may retry an upgrade after a short wait. The wait durations betweem retries are: 1m, 5m, 10m, 15m, 30m, 1h. During this time, the {agent} may show up as "retrying" in the {fleet} UI. Note that an -{agent} that is being retried, the upgrade may be aborted as detailed below. +upgrade that is being retried may be aborted as detailed below. 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 From 86ff3da23dbc36329bb69d54d8fa1b71cf37abc1 Mon Sep 17 00:00:00 2001 From: Michel Laterman <82832767+michel-laterman@users.noreply.github.com> Date: Tue, 11 Oct 2022 13:49:38 -0700 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: DeDe Morton --- .../ingest-management/fleet/upgrade-elastic-agent.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc index b679554a1e..cd412333e4 100644 --- a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc +++ b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc @@ -15,9 +15,9 @@ 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 betweem retries are: 1m, 5m, 10m, 15m, 30m, 1h. During this -time, the {agent} may show up as "retrying" in the {fleet} UI. Note that an -upgrade that is being retried may be aborted as detailed below. +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