Automatic Retries

Sometimes requests fail. When these requests fail for transient issues, Ambassador Edge Stack can automatically retry the request.

Retry policy can be set for all Ambassador Edge Stack mappings in the ambassador Module, or set per Mapping. Generally speaking, you should set retry policy on a per mapping basis. Global retries can easily result in unexpected cascade failures.

Configuring Retries

The retry_policy attribute configures automatic retries. The following fields are supported:

retry_policy:
retry_on: <string>
num_retries: <integer>
per_try_timeout: <string>

retry_on

(Required) Specifies the condition under which Ambassador Edge Stack retries a failed request. The list of supported values is one of: 5xx, gateway-error, connect-failure, retriable-4xx, refused-stream, retriable-status-codes. For more details on each of these values, see the Envoy documentation.

num_retries

(Default: 1) Specifies the number of retries to execute for a failed request.

per_try_timeout

(Default: global request timeout) Specify the timeout for each retry, e.g., 1s, 1500ms.

Examples

A per mapping retry policy:

---
apiVersion: getambassador.io/v1
kind: Mapping
metadata:
name: quote-backend
spec:
prefix: /backend/
service: quote
retry_policy:
retry_on: "5xx"
num_retries: 10

A global retry policy (not recommended):

---
apiVersion: getambassador.io/v1
kind: Module
metadata:
name: ambassador
spec:
config:
retry_policy:
retry_on: "retriable-4xx"
num_retries: 4
---
apiVersion: getambassador.io/v1
kind: Mapping
metadata:
name: quote-backend
spec:
prefix: /backend/
service: quote