Seems like what I really need is already discussed here: 
https://github.com/grpc/grpc-java/issues/1648
Still an open issue i'm afraid... 


On Sunday, November 27, 2016 at 6:50:09 PM UTC+2, Aryeh Weinreb wrote:
>
> Hi,
>
> I am trying to find a way to have my grpc c++ client detect that a service 
> has failed or changed location/IP.
>
> For now I use DNS to resolve the service's IP (and my services will 
> register themselves as they become available)
> The default 5 minute IDLE_TIMEOUT is too long.
> Is there any way to configure it or a TCP keep-alive  via the c++ library?
> Or is there a way to implement a resolver interface so I can detect 
> changes quicker?
>
> For now the only thing I can think of is to bring down and up the channel 
> based on failed RPC counts but I was wondering if there is a better way.
>
> Thanks,
> Aryeh
>
>
>

-- 
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/5e9690fb-68a3-470c-b4ce-ac00592e79c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to