-
Notifications
You must be signed in to change notification settings - Fork 712
Find the right home for maximum number of parallel retries #2322
Copy link
Copy link
Closed
Labels
Description
Description:
EG needs to find the right home for "maximum number of parallel retries"
- Option 1: par of the Circuit Breaker setting in BackendTrafficPolicy
- Option 2: par of the Retry setting in BackendTrafficPolicy
I prefer option 1 because:
Even though both have "retries" in their name, "maximum number of parallel retries" and "request retires" serve two different purposes. The concurrent max retries setting is inherently associated with the Circuit Breaker, which fails requests quickly when lot of retries happen and apply back pressure on downstream. On the other hand, request retries are specifically designed to mitigate transient network issues. Would love more insights from @kflynn and other @envoyproxy/gateway-maintainers
[optional Relevant Links:]
Reactions are currently unavailable