Tencent Cloud Mesh
- Release Notes and Announcements
- Announcements
- Getting Started
- Application Configuration
- Traffic Control
- Service HA
- Multi-cluster Disaster Recovery and Multi-active
- Security Reinforcement
- Operation Guide
- Mesh Instance Management
- Service Discovery Management
- Traffic Management
- Observability
- Access Management
- Extended Features
- FAQs
Circuit Breaking Does Not Take Effect
Last updated: 2023-12-26 15:30:30
http1MaxPendingRequests Not Defined
A DestinationRule is configured with
maxConnections.apiVersion: networking.istio.io/v1beta1kind: DestinationRulemetadata:name: nginxspec:host: nginxtrafficPolicy:connectionPool:tcp:maxConnections: 1
However, the test result shows that when the number of concurrencies exceeds the maximum number of connections defined, circuit breaking is not triggered but the QPS is very low. Usually, this is because the
http1MaxPendingRequests field is not configured. If the field is not configured, the default value 2^32-1 is used, which is very large. This setting indicates that if the maximum number of connections is exceeded, the request will be queued first (503 will not be returned directly). When the number of connections falls below the maximum value, forwarding will continue.If you want circuit breaking to be triggered (503 is returned) when the number of connections reaches the upper limit or exceeds the upper limit for a certain amount, you need to explicitly specify
http1MaxPendingRequests.apiVersion: networking.istio.io/v1beta1kind: DestinationRulemetadata:name: nginxspec:host: nginxtrafficPolicy:connectionPool:tcp:maxConnections: 1http:http1MaxPendingRequests: 1
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No