Istio’s DestinationRule tcp connectTimeout is 10s default, and if we set VirtualService http Timeout to 30s. A http request will be timeout if over 10s, then if we reset tcp connectTimeout in DestinationRule, how to make it effective immediately? Thanks.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Connection Pool behavior for cluster service vs. external service? | 0 | 435 | February 22, 2022 | |
| Connection reset error when using Istio VS to create a proxy | 0 | 1916 | May 23, 2022 | |
| Istioctl for the pod is not showing the timeout setting on the virtual service configuration | 1 | 927 | November 27, 2019 | |
| VirtualService per-destination timeouts and retries | 0 | 1566 | October 24, 2020 | |
| Application HTTP Keep Alive issues with Istio | 2 | 7079 | May 26, 2021 |