You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hangfire Server handles storage outages by catching exceptions, log them and use retry logic with exponential/random delay to repair automatically after some time. Since I don't like to have infinite loops, I've limited retry attempts count (max 10 retries). However, this means that DevOps team should always repair Hangfire storage in less than ~5 minutes. Or processing will be stopped, and you'll have to restart Hangfire Server manually.
So in this place it is better to have infinite number of attempts (at least by default) and have maximum delay set to a suitable value (to prevent very long delays).
The text was updated successfully, but these errors were encountered:
Hangfire Server handles storage outages by catching exceptions, log them and use retry logic with exponential/random delay to repair automatically after some time. Since I don't like to have infinite loops, I've limited retry attempts count (max 10 retries). However, this means that DevOps team should always repair Hangfire storage in less than ~5 minutes. Or processing will be stopped, and you'll have to restart Hangfire Server manually.
So in this place it is better to have infinite number of attempts (at least by default) and have maximum delay set to a suitable value (to prevent very long delays).
The text was updated successfully, but these errors were encountered: