Skip to content

fix: transient error log-spam, add retry policy #1273

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

Merged
merged 5 commits into from
Mar 12, 2025

Conversation

toddbaert
Copy link
Member

@toddbaert toddbaert commented Mar 11, 2025

Fixes an issue observed when intervening proxies are used (like Istio), where the proxy's upstream is disconnected, resulting in immediate error responses from the proxy (which we still have a healthy TCP connection to) which causes a tight loop in our retry logic for a brief time until the upstream is available.

This PR adds a retry policy to retry such problematic requests, which also slows down our retry loop. In general this will make the provider more robust to transient errors in streams and unary calls. I will be adding something similar to the flagd spec.

Other minor refactors as well.

There is one possible enhancement we could consider as a separate issue, mentioned here.

@toddbaert toddbaert changed the title fix: transient error log-spam, add retry pol fix: transient error log-spam, add retry policy Mar 11, 2025
@toddbaert toddbaert force-pushed the fix/logspam-with-retry-pol branch from ff4efc1 to aafa689 Compare March 12, 2025 00:34
@toddbaert toddbaert force-pushed the fix/logspam-with-retry-pol branch from aafa689 to 934e191 Compare March 12, 2025 00:44
Signed-off-by: Todd Baert <[email protected]>
@toddbaert toddbaert requested a review from chrfwow March 12, 2025 12:00
@toddbaert toddbaert merged commit 245e9ed into main Mar 12, 2025
5 checks passed
@toddbaert toddbaert deleted the fix/logspam-with-retry-pol branch March 12, 2025 14:09
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

Successfully merging this pull request may close these issues.

6 participants