GitHub user lhotari edited a comment on the discussion: DNS

> @lhotari We tried adding the additional trailing dot and fully qualified name 
> and that works and stops the search for additional domains . But where as 
> other consumer application we give short names and it works fine but where as 
> pulsar requires this FQDN. Which is actually a concern from the consuming 
> endpoints .

Why is it a concern? Please share sufficient context so that it would be 
possible to under stand the concerns.

> Is there any way to stop this search of searchdomains using short name for 
> services .

Since extra DNS lookups stop by using the FQDN name, it seems that you can 
already stop it. 

It's possible that the unnecessary connection attempts shouldn't even be 
stopped. We'll have to take a closer look at the problem in Pulsar client to 
know whether it's correct behavior or not.

This is the diff [between Netty 4.1.116.Final and 
4.1.118.Final](https://github.com/netty/netty/compare/netty-4.1.116.Final...netty-4.1.118.Final).
 Possible DNS resolution impacting change is 
https://github.com/netty/netty/commit/1bd459ac11ff8486641e619abdd732c7bbd94c70 
/ https://github.com/netty/netty/pull/14658, however it's unlikely that it 
would impact k8s deployments.

On the Pulsar side, this is a recent change in DNS resolution: 
https://github.com/apache/pulsar/pull/23590
Regarding lookups and DNS resolution in the Pulsar client, I found a bug fix 
that doesn't seem to have been cherry-picked to 3.x: 
https://github.com/apache/pulsar/pull/23260 . Another impactful change in this 
case could be https://github.com/apache/pulsar/pull/23378 .  Please test with 
the most recent Pulsar client 4.0.3 to see if your problem reproduces with it, 
unless you are already using Pulsar client 4.0.3.

@sindhushreem25 What Pulsar client version gives you the desired behavior and 
which version doesn't? Would you be able to provide a reproducer of your 
problem? A standalone repository or gist.github.com would be fine for sharing 
exact details. By contributing a proper reproducer, it's a great way to 
contribute to the project. When there's a reproducer, it's usually easy to fix 
the actual issue. That's why it matters for project maintainers.

GitHub link: 
https://github.com/apache/pulsar/discussions/24030#discussioncomment-12385104

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to