From 353baab8d413140064051fccf5b73dce54ce72c6 Mon Sep 17 00:00:00 2001 From: Vahid Farahmandian Date: Tue, 27 Jul 2021 01:04:29 +0430 Subject: [PATCH] Update retries.md (#22850) Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Co-authored-by: James Newton-King --- aspnetcore/grpc/retries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/grpc/retries.md b/aspnetcore/grpc/retries.md index 9530d0b458..e6e555fa9f 100644 --- a/aspnetcore/grpc/retries.md +++ b/aspnetcore/grpc/retries.md @@ -163,7 +163,7 @@ The following table describes options for configuring gRPC hedging policies: | Option | Description | | ------ | ----------- | | `MaxAttempts` | The hedging policy will send up to this number of calls. `MaxAttempts` represents the total number of all attempts, including the original attempt. This value is limited by `GrpcChannelOptions.MaxRetryAttempts` which defaults to 5. A value is required and must be 2 or greater. | -| `HedgingDelay` | The first call will be sent immediately, but the subsequent hedging calls will be delayed by this value. When the delay is set to zero or `null`, all hedged calls are sent immediately. Default value is zero. | +| `HedgingDelay` | The first call is sent immediately, subsequent hedging calls are delayed by this value. When the delay is set to zero or `null`, all hedged calls are sent immediately. `HedgingDelay` is optional and defaults to zero. A value must be zero or greater. | | `NonFatalStatusCodes` | A collection of status codes which indicate other hedge calls may still succeed. If a non-fatal status code is returned by the server, hedged calls will continue. Otherwise, outstanding requests will be canceled and the error returned to the app. For more information about status codes, see [Status codes and their use in gRPC](https://grpc.github.io/grpc/core/md_doc_statuscodes.html). | ## Additional resources