Skip to content

Istio default retry strategy is transparently retrying POST requests that connected fine #13851

@Stono

Description

@Stono

As you can see from this trace, a POST request reached vehicle-metric-service, and for some unknown reason (likely #13848) it 503's mid processing.

It was then retried by the default retry policy.

I really do not think the default retry policy should retry anything which successfully connected, only connection errors. @nmittler I know we've talked about this before but couldn't find the associated thread.

Screenshot 2019-05-06 at 21 48 50

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/networkinglifecycle/staleproofIndicates a PR or issue has been deemed to be immune from becoming stale and/or automatically closed

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions