Dataplane Timeouts

Substrate dataplane timeouts are tuned to support streaming or long running requests, such as inference. Timeouts for ingress and egress traffic are the same. On the ingress path timeouts are defined for connections and requests between client and actor, and on the egress path between actor and origin server. Internal CONNECT tunnels between Atunnel and Ingress or Egress gateways are transparent to the traffic and do not have configured timeouts.

1 min read ·

Substrate dataplane timeouts are tuned to support streaming or long running requests, such as inference. Timeouts for ingress and egress traffic are the same. On the ingress path timeouts are defined for connections and requests between client and actor, and on the egress path between actor and origin server. Internal CONNECT tunnels between Atunnel and Ingress or Egress gateways are transparent to the traffic and do not have configured timeouts.

TimeoutDescriptionDefault ValueUser Configurable
Idle connection timeoutTimeout for connections without outstanding requests.5 minutesNo
Maximum connection durationMaximum lifetime of a connection.DisabledNo
Request timeoutMaximum time for request headers, body and trailers (if present) to be received.DisabledNo
Request headers timeoutMaximum time for request headers to be received.10 secondsNo
Request idle timeoutTimeout for requests without network activity.DisabledNo
Maximum request durationMaximum lifetime of a request from the start to the end of response.DisabledNo
Response timeoutTimeout for response to be fully received.5 minutesYes. See –route-timeout
TLS handshake timeoutTimeout for compltetion of TLS handshake.10 secondsNo
Was this page helpful?