Skip to content
New issue

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

x-envoy-upstream-rq-per-try-timeout-ms timeouts *are* retried #101

Merged
merged 2 commits into from
Sep 27, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions docs/configuration/http_filters/router_filter.rst
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,12 @@ using a ',' delimited list. The supported policies are:
Envoy will attempt a retry if the upstream server responds with any 5xx response code, or does not
respond at all (disconnect/reset/etc.). (Includes *connect-failure* and *refused-stream*)

* **NOTE:** Envoy will not retry when a request times out (resulting in a 504 error code). This is
by design. The request timeout is an outer time limit for a request, including any retries that
take place.
* **NOTE:** Envoy will not retry when a request exceeds
:ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms` (resulting in a 504 error
code). Use :ref:`config_http_filters_router_x-envoy-upstream-rq-per-try-timeout-ms` if you want
to retry when individual attempts take too long.
:ref:`config_http_filters_router_x-envoy-upstream-rq-timeout-ms` is an outer time limit for a
request, including any retries that take place.

connect-failure
Envoy will attempt a retry if a request is failed because of a connection failure to the upstream
Expand Down