GitHub user lhotari added a comment to the discussion: DNS
> We are on pulsar 3.0.6 and i had to cherry pick the netty fix because of > security vulnerability .post that the behavior changed. Newer Pulsar clients are compatible with older broker versions. Would you be able to test with Pulsar client 4.0.3 to see if there's any difference in behavior compared to what you are seeing? This would help isolate the problem if you'd help doing this part on your side. > [pulsar@itomdipulsar-bastion-0 pulsar]$ cat /etc/resolv.conf > search op.svc.cluster.local svc.cluster.local cluster.local > nameserver 172.17.0.78 > options ndots:5 Is this the DNS configuration on the client side? Regarding the problem itself, it could be useful to share more logs (it's fine to sanitize before sharing) as a [GitHub gist](https://gist.github.com/). The previously shared logs are too brief. GitHub link: https://github.com/apache/pulsar/discussions/24030#discussioncomment-12386527 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
