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

Back-off strategy for calling Unleash #141

Closed
dramamask opened this issue Sep 28, 2023 · 2 comments
Closed

Back-off strategy for calling Unleash #141

dramamask opened this issue Sep 28, 2023 · 2 comments

Comments

@dramamask
Copy link

Describe the feature request

I'd like to see some kind of back-off strategy when it comes to calling the Unleash API. Basically a circuit breaker pattern or something to that extend. Right now the code seems to immediately retry calling Unleash after a failed attempt. I'd also be happy with a setting where I can determine the retry time-out.

Background

We recently had an issue where we couldn't reach Unleash. The unleash go client kept trying to call Unleash, about every 50 milliseconds (i.e. about 20 times per second). This lead to literally millions of error messages in our logs. Our DevOps guys were not happy.

Solution suggestions

You could implement a circuit-breaker pattern, or maybe just a configurable retry time-out.

@daveleek
Copy link
Contributor

daveleek commented Oct 2, 2023

Hi @dramamask, thanks for raising this. This is a planned project for Q4 - I've added it to the public roadmap

Issue: Unleash/unleash#4904
Public roadmap: https://github.com/orgs/Unleash/projects/10

Copy link

stale bot commented Nov 2, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 2, 2023
@stale stale bot closed this as completed Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants