[
https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin....
]
Sebastian Łaskawiec commented on JGRP-2316:
-------------------------------------------
[~belaban] This behavior is possible for example with AWS DNS Service. In JGRP-2300, one
of the users reported such a behavior, that the DNS Service dynamically remaps the ports.
Here's an example DNS SRV response:
{code}
$ dig jgroups.dev.auth.example.com.svc.cluster.local SRV
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.58.amzn1 <<>>
jgroups.dev.auth.example.com.svc.cluster.local SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16690
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;jgroups.dev.auth.example.com.svc.cluster.local. IN SRV
;; ANSWER SECTION:
jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32921
9ec82e3f-3a0e-4e30-b785-17879c63cd7d.jgroups.dev.auth.example.com.svc.cluster.local.
jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32923
60b5a820-9678-4bd2-84c6-00061a52bde0.jgroups.dev.auth.example.com.svc.cluster.local.
jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32915
9d9d78d0-8919-4b91-9df8-2e4e65afedae.jgroups.dev.auth.example.com.svc.cluster.local.
jgroups.dev.auth.example.com.svc.cluster.local. 10 IN SRV 1 1 32917
161f3d66-f1e3-46f4-a44f-ebda925a25c6.jgroups.dev.auth.example.com.svc.cluster.local.
;; Query time: 2 msec
;; SERVER: 10.42.3.2#53(10.42.3.2)
;; WHEN: Fri Sep 21 01:45:44 2018
;; MSG SIZE rcvd: 481
{code}
We also have a pull request to fix this:
https://github.com/belaban/JGroups/pull/409. Let
me close the other issue (JGRP-2300) since this one has more information and a pull
request.
DNS_PING is not using correct ports with SRV based service discovery
--------------------------------------------------------------------
Key: JGRP-2316
URL:
https://issues.jboss.org/browse/JGRP-2316
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.15
Reporter: dmcnair
Assignee: Bela Ban
Priority: Major
This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve
the port for SRV records. While that change is working as desired, `DNS_PING.java` is not
using the port when doing member discovery.
Here are the log entries using *4.0.15*
{noformat}
2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null)
Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105]
2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null)
982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105]
on ports [7600 .. 7600]
{noformat}
Since the port was found via the SRV record, it should be used instead of the
*transportPort* port.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)