We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
在 DestinationRule 配置中,我们定义了 maxConnections: 1 和 http1MaxPendingRequests: 1。 这些规则意味着,如果并发的连接和请求数超过 1 个,在 istio-proxy 进行进一步的请求和连接将被阻止。 于是,当我们并发数为 30 时,成功率只有 1/30,也就是 3.3% 左右。
熔断,按照我的理解,要体现断,体现上游服务被摘除,一旦熔断触发,一定时间的窗口期内,该上游服务都不会接收到请求;
如果是发出的请求,有1/30是成功的,那说明链路是通的,这叫限流,不叫熔断吧?如果上游服务由于内部故障导致响应一直超时,那么只要不熔断,下游服务就会被拖慢,限流解决不了这个问题。
个人见解,盼解惑!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
熔断,按照我的理解,要体现断,体现上游服务被摘除,一旦熔断触发,一定时间的窗口期内,该上游服务都不会接收到请求;
如果是发出的请求,有1/30是成功的,那说明链路是通的,这叫限流,不叫熔断吧?如果上游服务由于内部故障导致响应一直超时,那么只要不熔断,下游服务就会被拖慢,限流解决不了这个问题。
个人见解,盼解惑!
The text was updated successfully, but these errors were encountered: