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 5:31 AM, 谭锦彪 <mirendet...@gmail.com> wrote:

> 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/4    00:00:00 ./greeter_server 5051
> root     16034 15945  0 20:19 pts/8    00:00:00 ./greeter_server 5052
>
> I want to combine grpc with consul, cause grpc do not support registration
> and discovery. so when I start multi process in one server, the client can
> not distingusih it.
> and there are port in the DNS SRV records, for example:
>
> dig @localhost -p 8600 sag-test-grpc.service.consul-dev. SRV
>
> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6 <<>> @localhost -p 8600
> sag-test-grpc.service.consul-dev. SRV
> ; (2 servers found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23645
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;sag-test-grpc.service.consul-dev. IN SRV
>
> ;; ANSWER SECTION:
> sag-test-grpc.service.consul-dev. 0 IN SRV 1 1 *5052*
> sag-adsbackend-RTB-bjdx-10.110.28.11-test.node.bjdx.consul-dev.
> sag-test-grpc.service.consul-dev. 0 IN SRV 1 1 *5051*
> sag-adsbackend-RTB-bjdx-10.110.28.11-test.node.bjdx.consul-dev.
>
> ;; ADDITIONAL SECTION:
> sag-adsbackend-RTB-bjdx-10.110.28.11-test.node.bjdx.consul-dev. 0 IN A
> 10.110.28.11
> sag-adsbackend-RTB-bjdx-10.110.28.11-test.node.bjdx.consul-dev. 0 IN A
> 10.110.28.11
>
> ;; Query time: 1 msec
> ;; SERVER: 127.0.0.1#8600(127.0.0.1)
> ;; WHEN: Sat Aug 12 20:19:49 2017
> ;; MSG SIZE  rcvd: 174
>
> And I find grpc parse the DNS SRV records for some other informations in
> this proposal:
> https://github.com/grpc/proposal/blob/master/A5-grpclb-in-dns.md
>
> So, why not parse the port too?
>
> 在 2017年8月11日星期五 UTC+8下午10:48:11,Mark D. Roth写道:
>>
>> 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, 谭锦彪 <miren...@gmail.com> wrote:
>>
>>> 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 the gRFC process, please keep discussion in this thread.  All
>>>> comments welcome.
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> Mark D. Roth <ro...@google.com>
>>>> Software Engineer
>>>> Google, Inc.
>>>>
>>> --
>>> 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+u...@googlegroups.com.
>>> To post to this group, send email to grp...@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/ms
>>> gid/grpc-io/1b0a00e9-d9fd-4c85-87ea-46d35e69a4c6%40googlegroups.com
>>> <https://groups.google.com/d/msgid/grpc-io/1b0a00e9-d9fd-4c85-87ea-46d35e69a4c6%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Mark D. Roth <ro...@google.com>
>> Software Engineer
>> Google, Inc.
>>
> --
> 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/8ebc89ce-fcf1-4599-96b7-3c134f2107e9%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/8ebc89ce-fcf1-4599-96b7-3c134f2107e9%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Mark D. Roth <r...@google.com>
Software Engineer
Google, Inc.

-- 
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/CAJgPXp6EhhME%3DPyP%3DpgFqcHVFvPKyCWf-%3DrYGuaReVbup2Y2OA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to