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.

Sign up for GitHub

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

Jump to bottom

MeshRetry do not allow retry GRPC connection errors #12931

Open
tony-bondarenko opened this issue Feb 24, 2025 · 0 comments
Open

MeshRetry do not allow retry GRPC connection errors #12931

tony-bondarenko opened this issue Feb 24, 2025 · 0 comments
Labels
kind/feature New feature triage/needs-reproducing Someone else should try to reproduce this

Comments

@tony-bondarenko
Copy link

Description

All MeshRetry retryOn options available for grpc protocol (Canceled, DeadlineExceeded, Internal, ResourceExhausted, Unavailable) only trigger retry in case http headers are returned from the grpc service.
If request failure is related to connection issues (reset, timeout), no retry is triggered.

Such options are available for http protocol: Reset, ConnectFailure. Also 5xx is a combination of these.
But http MeshRetry policy is filtered out if service port has appProtocol = grpc and is not being applied.
@tony-bondarenko tony-bondarenko added kind/feature New feature triage/pending This issue will be looked at on the next triage meeting labels Feb 24, 2025
@bartsmykla bartsmykla added triage/needs-reproducing Someone else should try to reproduce this and removed triage/pending This issue will be looked at on the next triage meeting labels Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/needs-reproducing Someone else should try to reproduce this
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tony-bondarenko @bartsmykla