Thanks Ken, do you know if/where we can details on that work?
--
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
The overall conclusion is correct that the client library will
transparently retry only in the case where there is a protocol level
guarantee that the server has not executed the RPC. However, this guarantee
may be available even for some RPCs that return INTERNAL error code and the
library is
I think you must be looking at code that does not include that PR. With
that PR, there are no calls to grpc_lb_addresses_set_address() in
dns_resolver_ares.c; those calls have been moved to grpc_ares_wrapper.c,
and the is_balancer parameter is set to true for balancer addresses:
gRPC only uses SRV records for grpclb, as described in this gRFC. It does
not use them for backend addresses, and we have no plans to change that.
If you want to implement your own system for service discovery on top of
DNS, you can write your own resolver plugin for gRPC.
On Sat, Aug 12, 2017
Thanks a lot, thinks that what I need, so sorry I haven't get time to
prepare the code snippet.
On Friday, August 11, 2017 at 3:16:59 AM UTC+8, Eric Anderson wrote:
>
> I think you can do this with a server interceptor. Simply delay calling
> next until the configuration is available.
>
> On
