Skip to content
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

Canonical way to handle error bursting #187

Open
truekonrads opened this issue Jan 4, 2023 · 0 comments
Open

Canonical way to handle error bursting #187

truekonrads opened this issue Jan 4, 2023 · 0 comments

Comments

@truekonrads
Copy link

Hello,

What would be the canonical way to handle error bursting and enter an "error-disable" state?

Imagine you have a very long running function, such as HTTP polling, which from time to time may thrown an exception that should be handled using classic backoff approach. However, sometimes there are too many exceptions in a short period of time and you want to propagate the exception upwards or otherwise just exit. If I simply accumulate number of exceptions using max_tries then over a longer period the exceptions will accumulate.
In short one exception every hour is OK, but 10 exceptions in an hour are not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant