You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is no way to actively detect errors for specific connections and terminate connections that are unhealthy.
It would be useful when a server uses a load balancer as its endpoint. A host-level circuit breaker is not effective when a specific server behind the LB is not operating. If there are two servers and one server does not operate properly, the circuit may become open.
Motivation:
Currently, there is no extension point to detect errors for specific
connections and terminate connections that are unhealthy.
Related: line#5751
Modifications:
- TBU
Result:
Currently, there is no way to actively detect errors for specific connections and terminate connections that are unhealthy.
It would be useful when a server uses a load balancer as its endpoint. A host-level circuit breaker is not effective when a specific server behind the LB is not operating. If there are two servers and one server does not operate properly, the circuit may become open.
We may provide a
OutlierDectionRule
, similar toCircuitBreakerRule
, to let users decide whether to close the connection if necessary.https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/outlier
The text was updated successfully, but these errors were encountered: