I have been searching for an existing solution that employs a backoff algorithm when a Job needs re-executed because of a 'recovery' or 'failover' is encountered.
I have a task that in normal cases may fail because resources are offline for a few hours. I don't want retries to keep being immediate; I want to use a simple backoff algorithm.
If there is no prescribed solution, I'll share what I write.
![[Logo]](/forums/templates/default/images/logo.png){kind=logo}
![[Expert]](/img/training.png)
![[Search]](/forums/templates/default/images/icon_mini_search.gif){kind=icon}
![[Recent Topics]](/forums/templates/default/images/icon_mini_recentTopics.gif){kind=icon}
![[Members]](/forums/templates/default/images/icon_mini_members.gif){kind=icon}
![[Groups]](/forums/templates/default/images/icon_mini_groups.gif){kind=icon}
![[Register]](/forums/templates/default/images/icon_mini_register.gif){kind=icon}
Register![[Login]](/forums/templates/default/images/icon_mini_login.gif){kind=icon}
Login
