GitHub user sindhushreem25 added a comment to the discussion: DNS
@lhotari its not about the extra dot in the DNS names . its like if we have 3 DNS names resolved like a.b.c ,x.y.z and p.q.r.s a.b.c is correct one and it resolves and connects .but where as in the logs we still see its trying to connect to x.y.z and other one which is wrong and fails .its trying for every connection it looks like .this behavior is see post netty upgrade to 118. with netty 116 it tries with one address and waits there if it fails or succeeds WARN org.apache.pulsar.client.impl.ConnectionPool - [[id: 0x7a0a4f2b, L:/172.16.3.21:38920 ! R:pulsar-proxy.xx.xxx.cluster.local/xxx.xx.xx.xxx:6651]] Connection handshake failed: org.apache.pulsar.client.api.PulsarClientException: Connection already closed but with 118 its trying to resolve the next dns in some interval and printing the below warn messages irrespective of the other one connects successfully also : org.apache.pulsar.client.impl.ConnectionPool - Failed to open connection to pulsar-proxy.op:6651 : org.apache.pulsar.shade.io.netty.resolver.dns.DefaultDnsCache$2: Failed to resolve GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12328641 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
