[
https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2316:
--------------------------------
The ports reported by DNS (A or SRV records) are *irrelevant* (in that respect, I think
JGRP-2996 is irrelevant, too): the ports are defined in the JGroups config *only*, as
Kubernetes/Openshift only knows the IP addresses of the started pods, but not the JGroups
ports!
So what DNS_PING does is that it ignores the ports given by DNS, even if they're != 0.
Instead, it establishes connections to all IP addresses at range {{[TCP.bind_port ..
TCP.bind_port+port_range]}}.
If you don't agree, please show me a concrete example where this algorithm
wouldn't work. Meanwhile, I'm taking another look at JGRP-2996.
Cheers,
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)