Can't specify minimum delay when using retry_backoff
with jitter
#8503
Unanswered
bendavis78
asked this question in
Q&A
Replies: 1 comment
-
I agree, I'd like to be able to do something like ensure a third party API gets a whole hour to recover before we give up trying it (maybe to ride out rate limiting). I can do that by turning off jitter, but jitter is a good thing, I'd just like to be able to specify the minimum for jitter so that it chooses a random number in range(retry_jitter_min, retry_backoff+1) rather than range(0, retry_backoff+1). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
From the docs for
retry_backoff
:I understand jitter is added by default, but the above implies the first retry delay will be the number given in
retry_backoff
. However, with the current behavior, the first retry the countdown is often below the givenretry_backoff
number, as you can see in the following test:Is this expected behavior? It seems like we should have some way to control the minimum, but right now that doesn't seem to be possible.
Beta Was this translation helpful? Give feedback.
All reactions