-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
gRPC apps can make resilient API calls with client retry support #5493
Comments
What epic should this be listed under? |
@JamesNK any requirements on the client networking stack here? |
It was under cloud native. @richlander removed it. What was the reason behind that? |
Maybe. I will need to do some investigation then talk to client team |
OK, please let us know if there are. cc @karelz |
@glennc should this be parented somewhere in the Cloud Native Theme? |
This is done now, right @JamesNK ? |
Done! https://docs.microsoft.com/en-us/aspnet/core/grpc/retries?view=aspnetcore-6.0 A feature wasn't added in HttpClient, which is why some issues aren't closed, but I worked around it. |
Bulk closing .NET 6 epics and user stories. If you think this issue was closed in error, please reopen the issue and update it accordingly. |
Automatically retrying some failed API calls (i.e. connection failure, transient server error) is a common task in apps. Polly is an OSS library often used to support retries with RESTful APIs. Unfortunately Polly doesn't work with gRPC.
There is a gRPC specification for retrying failed calls - https://github.com/grpc/proposal/blob/master/A6-client-retries.md
The spec is implemented by the two first-class gRPC implementations: grpc-go and grpc-java. It is partially implemented by ccore and its related bindings (C++, PHP, Python, C#). There is currently no retry support in grpc-dotnet.
Reasons to do:
Dev features/work:
The text was updated successfully, but these errors were encountered: