diff options
| author |  Yash Tibrewal <yashkt@google.com> | 2018-07-25 11:16:08 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2018-07-25 11:16:08 -0700 |
| commit | 3df98c15f771f50ccc8842e7e55984e73f85aaa6 (patch) | |
| tree | 4d7451d1c4bd769bd7d18ad9514abf698a4439f0 | |
| parent | 6a2fbcb4d27243e8c32227b681c38c6221e09a00 (diff) | |
| parent | 600272c826b48420084c2ff76dfb0d34324ec296 (diff) | |
Merge pull request #16106 from grpc/yashykt-patch-1
Add note on retrying RPCs
| -rw-r--r-- | doc/statuscodes.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/statuscodes.md b/doc/statuscodes.md index f2df9e00de..06fbe5c8fe 100644 --- a/doc/statuscodes.md +++ b/doc/statuscodes.md @@ -38,6 +38,7 @@ situations in which they are generated. | Error parsing response proto | INTERNAL | Client| | Error parsing request proto | INTERNAL | Server| | Sent or received message was larger than configured limit | RESOURCE_EXHAUSTED | Both | +| Keepalive watchdog times out | INTERNAL | Both | The following status codes are never generated by the library: - INVALID_ARGUMENT @@ -47,3 +48,5 @@ The following status codes are never generated by the library: - ABORTED - OUT_OF_RANGE - DATA_LOSS + +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. |