Skip to content

Resilience filters: retry, circuit breaker, connection limits #38

@shaneutt

Description

@shaneutt

Without these, a misbehaving upstream or client can cascade failures through the proxy.

  • Retry: configurable policy, idempotency awareness, retry budget, retriable status codes (basic connect-retry exists but is hardcoded to 3 attempts, same backend)
  • Circuit breaker: per-cluster limits, consecutive error threshold, half-open probe state
  • Passive health checking / outlier detection

Note: Retry is partially implemented. Missing: configurable policy, retry budget, retriable status codes (502/503/504), per-route overrides, tried-endpoints tracking (avoid retrying same backend), body size threshold.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Next

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions