]
Bela Ban commented on JGRP-2316:
--------------------------------
[~sebastian.laskawiec] So how does Kubernetes DNS even *know* of the JGroups ports?
JGroups might even pick a completely random port, e.g. when {{FD_SOCK.bind_port =0}}.
Are you saying that the DNS maps *all* (UDP and TCP) ports of a process running in a
container to other, random ports? Would that only happen with SRV records?
Can you confirm that this is *not* for the ports configured in the YAML, e.g.
{noformat}
publishNotReadyAddresses: true
clusterIP: None
ports:
- name: ping
port: 8888
protocol: TCP
targetPort: 8888
selector:
deploymentConfig: jgrp
{noformat}
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.