From bcecc177a82ff150cfe98b42778180e3cff4d21d Mon Sep 17 00:00:00 2001 From: Yash Tibrewal Date: Tue, 24 Jul 2018 10:54:10 -0700 Subject: Update statuscodes.md Change wording --- doc/statuscodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/statuscodes.md') diff --git a/doc/statuscodes.md b/doc/statuscodes.md index 9fbd58b132..2cce38295e 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 -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. +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. -- cgit v1.2.3