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
Set RCD for 100% drop_overload case as unconditional_drop_overload (envoyproxy#38408)
This is a follow up commit of drop_overload
support:envoyproxy#30827.
It is observed that in some situations, EDS sends drop_overload ratio as
100% for some clusters do not have healthy endpoints in the cluster. For
such cases, it is preferred that the RCD of the local reply set to
"unconditional drop overload" to make it a little bit different from the
normal "drop overload" case.
---------
Signed-off-by: Yanjun Xiang <[email protected]>
Copy file name to clipboardExpand all lines: docs/root/configuration/observability/access_log/usage.rst
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -569,6 +569,7 @@ HTTP only
569
569
**DnsResolutionFailed**, **DF**, The request was terminated due to DNS resolution failure.
570
570
**DropOverload**, **DO**, The request was terminated in addition to 503 response code due to :ref:`drop_overloads<envoy_v3_api_field_config.endpoint.v3.ClusterLoadAssignment.Policy.drop_overloads>`.
571
571
**DownstreamRemoteReset**, **DR**, The response details are ``http2.remote_reset`` or ``http2.remote_refuse``.
572
+
**UnconditionalDropOverload**, **UDO**, The request was terminated in addition to 503 response code due to :ref:`drop_overloads<envoy_v3_api_field_config.endpoint.v3.ClusterLoadAssignment.Policy.drop_overloads>` is set to 100%.
0 commit comments