-
Notifications
You must be signed in to change notification settings - Fork 1.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
SDKs to support retry and reconnection to sidecar #6609
Comments
I have implemented a (tentative) reference implementation in the Java SDK. Users would have 2 environment variables to configure: I have tested this by using ToxiProxy with a jitter of 30 seconds, SDK configured with timeout of 10 seconds and 3 max retries. There is a significant different of how many of the calls to state store succeed after the policy is applied vs as-is. I also noticed that without the timeout config, the client will hang "forever" - so, these two settings go hand-in-hand IMO and should be applicable to both gRPC and HTTP protocols. |
I also bumped into a documentation for retries in the .Net gRPC client: https://learn.microsoft.com/en-us/aspnet/core/grpc/retries?view=aspnetcore-7.0 |
Work continues in 1.13, so far Java SDK is the only one that supports resiliency in 1.12. |
SDKs that support this feature:
We should strive to support this feature in all SDKs before closing this issue |
In what area(s)?
Describe the feature
DAPR_NETWORK_MAX_RETRIES
with default value of 3 (zero means disabled).DAPR_NETWORK_MAX_RETRIES
) to allow programmatically overwriting of the config when instantiating a client object.Proposal to follow after discussion here. In scope for 1.12
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: