Skip to content

Commit b2381e8

Browse files
Update reference/fleet/upgrade-elastic-agent.md
Co-authored-by: Visha Angelova <[email protected]>
1 parent 350925d commit b2381e8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

reference/fleet/upgrade-elastic-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -248,7 +248,7 @@ To configure an automatic rollout of a new minor or patch version to a percentag
248248

249249
Once the configuration is saved, an asynchronous task runs every 30 minutes, upgrading the agents in the policy to the specified target version.
250250

251-
If the number of agents to be upgraded is greater or equal to 10, a rollout period based on this number is automatically applied.
251+
If the number of agents to be upgraded is greater than or equal to 10, a rollout period is automatically applied. The rollout duration is either 10 minutes or `nAgents * 0.03` seconds, whichever is greater.
252252

253253
In case of any failed upgrades, the upgrades are retried with exponential backoff mechanism until the upgrade is successful, or the maximum number of retries is reached. Note that the maximum number of retries is the number of [configured retry delays](#auto-upgrade-settings).
254254

0 commit comments

Comments
 (0)