-
-
Notifications
You must be signed in to change notification settings - Fork 77
Retry middleware #281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Retry middleware #281
Conversation
Problem: The RequestSchedulerInterface was not registered as a singleton/shared in the dependency injection container. Because of this, the Engine received one instance of the scheduler, while the RetryMiddleware received a completely different, new instance. As a result, they operated with separate queues.
'retryOnStatus' => [500, 502, 503, 504], | ||
'maxRetries' => 3, | ||
'initialDelay' => 1000, | ||
'delayMultiplier' => 2.0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer if we combined initialDelay
and delayMultiplier
into a single backoff
option that takes an array of integers.
So a backoff of [1, 5, 10]
would mean the first retry happens after one second, the second after 5, the third after 10 seconds and 10 seconds for every subsequent request if maxRetries
is greater than 3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good idea. Implemented.
Thanks for the PR! Looks good overall but I have a few comments that need to be addressed first. Please check them out when you find the time. |
No description provided.