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

Handle sending failures #7

Open
6 tasks
federico-razzoli opened this issue Mar 25, 2022 · 1 comment
Open
6 tasks

Handle sending failures #7

federico-razzoli opened this issue Mar 25, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@federico-razzoli
Copy link
Member

federico-razzoli commented Mar 25, 2022

  • When a client succeeds, max_failures is set to 0 and the client state is OK.

  • If a client fails max_failures times, it should enter the FAIL state. The timestamp of this failure is also remembers.

  • After an interval, the state changes to TRY. This interval length depends on the backoff factor.

  • Only use clients that are configured and (OK or TRY).

  • If the state is TRY and the client fails, it switched to FAIL, and its retry_interval is set to max(power(retry_interval, 2), max_retry_interval).

  • If the state is TRY and the client succeeds, its retry_interval is set to the original value.

@federico-razzoli federico-razzoli added the enhancement New feature or request label Mar 25, 2022
@federico-razzoli
Copy link
Member Author

For HTTP, we're now using the Request module's backoff strategy.

When we implement this task we should stop using it, and we should implement a global backoff.

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

No branches or pull requests

1 participant