Retry is already implemented (except hedging support) in v1.16.1, but there is no other document than the spec yet, because there are some caveats for the time being: (1) users need manage to disable census stats and tracing when enabling retry,(2) there are some caveats for using service config. In next release, v1.17.0, enabling retry will automatically disable census.
As for DEADLINE_EXCEEDED, it does not make sense to retry at the library level, because a retry attempt would immediately exceed the deadline of the RPC. Users could implement application level retry for DEADLINE_EXCEEDED by themselves by making a new RPC. On Monday, November 5, 2018 at 12:55:42 PM UTC-8, David M wrote: > > I am trying to find a document describing grpc java retry behavioral. > All I was able to find is this proposal : > https://github.com/grpc/proposal/blob/master/A6-client-retries.md > It's not clear what is already implemented. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/69f00deb-c65c-4bdc-9d71-8e67d90e0e02%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
