Skip to content

Commit 1160d22

Browse files
committed
PB-2395: name the algo consistently
1 parent ab5e878 commit 1160d22

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

get-started/retry.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Retry strategy
22

33
For any request that you want to retry automatically, we recommend that you do
4-
so using a jittered exponential backoff algorithm.
4+
so using a truncated exponential backoff algorithm with jitter.
55

66
## Overview
77

@@ -12,9 +12,10 @@ some care to do correctly as incorrect retry strategies may cause many requests
1212
to be (re)sent in a short amount of time, which may eventually cause them to be
1313
throttled or otherwise permanently dropped. To mitigate this
1414
[thundering herd problem](https://en.wikipedia.org/wiki/Thundering_herd_problem),
15-
we recommend you implement retries with jittered truncated exponential backoff.
15+
we recommend you implement retries using a truncated exponential backoff with
16+
jitter.
1617

17-
## Jittered truncated exponential backoff algorithm
18+
## Truncated exponential backoff algorithm with jitter
1819

1920
Here is an example of algorithm that implements the recommended retry strategy:
2021

0 commit comments

Comments
 (0)