-
Notifications
You must be signed in to change notification settings - Fork 518
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
Non-blocking backOff policy #25
Comments
+1 |
Is it not meant to make us of a stateful retry for such an use case? I also have a long living retry and need that feature too. But can't really get stateful retry to work. |
+1 |
+1 any update? |
Just use this library which achieves exactly what you want. I've been using it in several production systems for like 5 years - works great! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would like to have a backOff policy that does not block the thread of execution. The use-case for this is roughly having a long-lived job that is comprised of many short-lived steps, where some step in the sequence retries potentially many times for a long period. Freeing up the thread will allow steps from other jobs to be executed during the blocking step's backOff period.
The text was updated successfully, but these errors were encountered: