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 at
Thanks for your response, maybe my environment has some problem, I will
study it .
在 2017年8月11日星期五 UTC+8下午11:00:10,Mark D. Roth写道:
>
> 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/f
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 .
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 grpc_ares_ev_dri
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 support
> port. Thus wil
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 t
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 grpc_ares_wrappe
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 implementation
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(
"dns://localhost:8600/sag_test_grpc.service.consul-dev
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:
>
> https://github.com/grpc/proposal/pull/10
10 matches
Mail list logo