-
Notifications
You must be signed in to change notification settings - Fork 3.9k
examples: Adds client/server retrying example via service config #7111
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
Conversation
|
40b5cc3
to
87f4770
Compare
87f4770
to
d85e6f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add a session here for retry, similar for hedging example?
709dcd1
to
ca99a05
Compare
@dapengzhang0 added a section to the README. hope it looks ok 👍 |
any idea why the "Macos" pipeline check could be stuck on "waiting"? I'm unfamiliar with the CI integrations... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Those tests are manually triggered by project owners for external user's PRs. No worries. |
@alexanderscott, thank you! |
Provides an example HelloWorld GRPC client & server which demos the effect of client retry policy configured to the ManagedChannel via GRPC ServiceConfig.
Retry policy configuration is outlined in its proposal, and this example is very similar to the Hedging Example.
I created this example to prove that client GRPC retry via service config does indeed work (although still marked as experimental). Also wrote an example and tests using client future unary calls, but figure this simple example is sufficient.