Shubham Ranjan
Shubham Ranjan
Can you elaborate with an example showing the behavior of how would you like to use the client ?.
@ElderJames This is exactly what you want right ? : https://etcd.io/docs/v3.3.12/dev-guide/grpc_naming/
@satishviswanathan Do you get any sort of exception on etcd server restart ?
Noted. Etcd restarts haven't been handled yet for etcd watches are neither is there a provision for an exception handler. This are is something we need to improvise on. @yoricksmeets...
@yanhua1012 Can you explain a bit as it happens ?. For e.g. 1. 1 node goes down, 1 error occurs and subsequent work and so on.......
Thanks @setood . I see a lot of great features have been added to the grpc client. I will try to re design the whole client again. IMO, I think...
I will check how they have implemented and get back on this one. Cannot see an grpc parameter provided in their contract.
The grpc api currently doesn't have a parameter exposed. Hence, cannot add this feature atm. Will raise an issue and see what response do I get from them. Ref: https://etcd.io/docs/v3.3.12/dev-guide/api_reference_v3/#service-cluster-etcdserveretcdserverpbrpcproto
Thats the v2 api which supports the rest protocol only. gRPC is supported with v3+ (which this library is built on top of) and the grpc contract of etcd server...
> addReq.PeerURLs.Add("testName=http://localhost:1234"); //just example This format doesn't seem to be supported as of now.