diff options
| author |  Yash Tibrewal <yashkt@google.com> | 2018-07-24 11:15:10 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2018-07-24 11:15:10 -0700 |
| commit | 600272c826b48420084c2ff76dfb0d34324ec296 (patch) | |
| tree | db65afd018c0ea7966eaea0bdb932a31192c351a /doc/statuscodes.md | |
| parent | bcecc177a82ff150cfe98b42778180e3cff4d21d (diff) | |
Update statuscodes.md
Add link to retry doc
Diffstat (limited to 'doc/statuscodes.md')
| -rw-r--r-- | doc/statuscodes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/statuscodes.md b/doc/statuscodes.md index 2cce38295e..06fbe5c8fe 100644 --- a/doc/statuscodes.md +++ b/doc/statuscodes.md @@ -49,4 +49,4 @@ The following status codes are never generated by the library: - OUT_OF_RANGE - DATA_LOSS -Applications that may wish to retry failed RPCs must decide which status codes on which to retry. As shown in the table above, the gRPC library can generate the same status code for different cases. Server applications can also return those same status codes. Therefore, there is no fixed list of status codes on which it is appropriate to retry in all applications. As a result, individual applications must make their own determination as to which status codes should cause an RPC to be retried. +Applications that may wish to [retry](https://github.com/grpc/proposal/blob/master/A6-client-retries.md) failed RPCs must decide which status codes on which to retry. As shown in the table above, the gRPC library can generate the same status code for different cases. Server applications can also return those same status codes. Therefore, there is no fixed list of status codes on which it is appropriate to retry in all applications. As a result, individual applications must make their own determination as to which status codes should cause an RPC to be retried. |