fix: transient error log-spam, add retry policy #1273
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
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.