This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 43a861e8 correct docs for backoff on retry step
43a861e8 is described below
commit 43a861e83e9d28fba8d960f9e74d95d150eca0c7
Author: Alex Heneveld <a...@cloudsoft.io>
AuthorDate: Tue Jan 23 13:05:44 2024 +0000
correct docs for backoff on retry step
---
guide/blueprints/workflow/steps/steps.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/guide/blueprints/workflow/steps/steps.yaml
b/guide/blueprints/workflow/steps/steps.yaml
index 50bed277..6a338f7f 100644
--- a/guide/blueprints/workflow/steps/steps.yaml
+++ b/guide/blueprints/workflow/steps/steps.yaml
@@ -169,7 +169,7 @@
`JITTER` as either a percentage or real factor by which to jitter
the result with randomness, 0 being none, 100% being up to double, and -100%
being down to zero;
and `MAX` to specify a maximum duration; for example,
`backoff 1s 1s 10s` will retry after 1 second the first two times,
then after 10 seconds on subsequent instances;
- and `backoff 1s 2s backoff 3x max 1m` will retry after 1 second then
2s then 6s then 18s then 54s then 60s each subsequent time
+ and `backoff 1s 2s increasing 3x up to 1m` will retry after 1 second
then 2s then 6s then 18s then 54s then 60s each subsequent time
* `hash`: an optional hash expression to identify related retries in a
workflow instance; all retry blocks with the same `hash` will share counts
for the purpose of counting limits (although the limits themselves
are as per the definition in each retry block),
which can be useful if there are different steps which might fail in
different ways but the overall retry behaviour should be preserved
