GitHub user sindhushreem25 edited a discussion: Unnecessary DNS lookup errors in logs
"On a K8s deployment, when pulsar client is used from a namespace different from pulsar broker/proxy namespace we see unnecessary errors in logs which is misleading. Pulsar client is appending all the DNS search domains causing connection errors. This happens even post a valid name is identified for connecting to server." When we upgraded the netty to 118 in pulsar 3.0.X we are seeing a different behavior. in older version it used to resolve to one dns name and fail or pass the connection . 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 : 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 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
