envoyproxy/envoy
Ver no GitHubSub-Millisecond timeouts treated as no timeout
Open
#13.153 aberto em 17 de set. de 2020
area/httpbughelp wanted
Métricas do repositório
- Stars
- (27.997 stars)
- Métricas de merge de PR
- (Mesclagem média 8d) (378 fundiu PRs em 30d)
Description
Description: Timeouts are modeled as Duration and can accept nanos. If a route timeout is given nanos less than 1 millisecond, no timeout will be performed. 1 millisecond is the threshold for a timeout configuration. I did not yet test the same for other types of timeouts elsewhere.
Expected case is either a 504 gateway timeout or an updated document section. There may be valid usecases for sub-millisecond timeouts, but to me this usecase is not a priority, therefore I will leave it up to the team to decide best action.
Repro steps:
- match: { prefix: "/" }
route:
cluster: local_proxied_service
timeout:
nanos: 500000
#also try nanos: 1000000
#also try nanos: 1
Config:
- match: { prefix: "/" }
route:
cluster: local_proxied_service
timeout:
nanos: 500000