0

我有一项服务,我在其中添加了 5 分钟的延迟。因此,对该服务的请求将需要 5 分钟才能给出响应。现在我已经使用 istio v1.5 在 kubernetes 中部署了这个服务。当我通过入口网关调用此服务时,我会在 3 分钟内超时。

{"res_tx_duration":"-","route_name":"default","user_agent":"grpc-java-netty/1.29.0","response_code_details":"-","start_time":"****","request_id":"****","method":"POST","upstream_host":"127.0.0.1:6565","x_forwarded_for":"****","bytes_sent":"0","upstream_cluster":"****","downstream_remote_address":"****","req_duration":"0","path":"/****","authority":"****","protocol":"HTTP/2","upstream_service_time":"-","upstream_local_address":"-","duration":"180000","upstream_transport_failure_reason":"-","response_code":"0","res_duration":"-","response_flags":"DC","bytes_received":"5"}

我尝试将虚拟服务中的超时设置为大于 3 分钟,但这不起作用。只有在虚拟服务中设置的小于 3 分钟的超时有效。

route:
- destination:
    host: demo-service
    port:
      number: 8000
timeout: 240s

除了VirtualService,还有其他可以设置超时的配置吗?

3分钟(180s)是我们可以在VirtualService中设置的最大值吗?

4

0 回答 0