Add note on retrying RPCs

Also add keepalive to list.
pull/16106/head
Yash Tibrewal 7 years ago committed by GitHub
parent 25d2018029
commit 4ec08f7235
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 3
      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
The decision to retry RPCs at the application level depends on the application and the type of error. There is no single guidance that will work for all.

Loading…
Cancel
Save