Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-14 Thread 'Mark D. Roth' via grpc.io
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

Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-12 Thread 谭锦彪
Sorry for my pool english. When I say "multiprocess server", I mean multi process in a server with the same ip, but bind different port, for example: ps -ef | grep greeter_server root 15494 12990 0 20:17 pts/400:00:00 ./greeter_server 5051 root 16034 15945 0 20:19 pts/800:00:00

Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-11 Thread 'Mark D. Roth' via grpc.io
It works fine for me when building from master: D0811 07:57:48.380480115 16947 simple_request.c:116] client_peer_before_call=dns://127.0.0.1:1234/foo.com.:23164 D0811 07:57:48.380498101 16947 dns_resolver_ares.c:304]dns_ares_next is called. D0811 07:57:48.380896092 16947

Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-11 Thread 'Mark D. Roth' via grpc.io
I'm sorry, I don't follow your suggestion. What exactly do you mean by "parse the dns srv support port", and what use-case do you mean by "multiprocess server"? On Fri, Aug 11, 2017 at 2:29 AM, 谭锦彪 wrote: > A suggestion: why not parse the port use c-ares? as the dns srv

[grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-11 Thread 谭锦彪
A suggestion: why not parse the port use c-ares? as the dns srv support port. Thus will helpful to multiprocess server! 在 2017年2月1日星期三 UTC+8上午2:30:04,Mark D. Roth写道: > > I've put together the following gRFC for encoding grpclb data in DNS: > > https://github.com/grpc/proposal/pull/10 > > As per

Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-11 Thread 谭锦彪
Thank you so much for your response. Follow you suggest, I got this: D0811 14:07:29.205003940 20324 dns_resolver_ares.c:209]dns_ares_next is called. D0811 14:07:29.205322437 20324 grpc_ares_ev_driver_posix.c:127] grpc_ares_ev_driver_create I0811 14:07:29.205340232 20324

Re: [grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-08 Thread 'Mark D. Roth' via grpc.io
The feature you're asking about actually has nothing to do with supporting grpclb in DNS; it's actually about how to use an alternative DNS server for testing. I originally added support for specifying an alternative DNS server by IP address (not hostname) to the c-ares DNS resolver

[grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-08-08 Thread 谭锦彪
Hi,Roth. I got "dns_resolver.c:252] authority based dns uri's not supported", when use dns like below: ChannelArguments args; args.SetLoadBalancingPolicyName("round_robin"); GreeterClient greeter(grpc::CreateCustomChannel(

[grpc-io] Re: gRFC A5: Encoding grpclb info in DNS

2017-05-30 Thread 'David Garcia Quintas' via grpc.io
The document should be updated to mention https://github.com/grpc/grpc/pull/11237, perhaps once it's been merged. On Tuesday, 31 January 2017 10:30:04 UTC-8, Mark D. Roth wrote: > > I've put together the following gRFC for encoding grpclb data in DNS: > >