Skip to content

Commit ab5e878

Browse files
committed
PB-2395: s/max_backoff/max_delay/g
1 parent 01e7b31 commit ab5e878

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

get-started/retry.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,15 +28,15 @@ Here is an example of algorithm that implements the recommended retry strategy:
2828

2929
5. Upon retryable failure, wait 8 + `jitter` seconds before retrying.
3030

31-
6. And so on, with a delay of min(2<sup>n</sup> + `jitter`, `max_backoff`)
31+
6. And so on, with a delay of min(2<sup>n</sup> + `jitter`, `max_delay`)
3232
seconds at each iteration.
3333

3434
7. After `deadline` seconds, stop retrying the request.
3535

3636
The `jitter` value must be picked randomly at each iteration. In this example,
3737
it could be a fractional value between 0 and 1 second.
3838

39-
The `max_backoff` value defines the maximum time to wait between retries. You
39+
The `max_delay` value defines the maximum time to wait between retries. You
4040
should pick the highest value your use case can support. If you have no specific
4141
latency requirements, 2<sup>6</sup> (64) seconds should be reasonable in most
4242
situations.

0 commit comments

Comments
 (0)