Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make autodiscovery work based on SVC names and/or FQDN #145

Open
xrow opened this issue Aug 5, 2020 · 7 comments
Open

Make autodiscovery work based on SVC names and/or FQDN #145

xrow opened this issue Aug 5, 2020 · 7 comments

Comments

@xrow
Copy link
Contributor

xrow commented Aug 5, 2020

Problem: If the target endpoint is set to an name based value either a FQDN or a SVC name the member autodiscovery doen work. Though it does work when using a IP based host name target-endpoints: "XX.239.105.XX:30XXX"

The reason for this request is a simplyfied setup for HA.

@leszko
Copy link

leszko commented Aug 6, 2020

@xrow , target endpoint, do you mean:

  • WAN Replication?
  • Client Configuration?

DNS resolution works fine with the Hazelcast client. So you can put FQDN or SVC in the Hazelast client and it will successfully find the cluster.

Regarding WAN Replication, it is a general issue with Hazelcast that it does not resolve DNSes correctly. That's the related GH Issue: https://github.com/hazelcast/hazelcast-enterprise/issues/3627

@xrow
Copy link
Contributor Author

xrow commented Aug 6, 2020

Can see hazelcast/hazelcast-enterprise#3627, but it sound like this is the one i am talking about.

@Holmistr
Copy link

Holmistr commented Aug 7, 2020

@xrow Just to make sure, so the issue is happening when you're using WAN replication?

@xrow
Copy link
Contributor Author

xrow commented Aug 7, 2020

this is correct.

@Holmistr
Copy link

Holmistr commented Aug 7, 2020

@xrow I see, thank you. In that case, let me comment on it.
Working with hostnames in WAN replication is our long standing issue. However, it's not trivial at all to fix. Therefore, we are scheduling it for the next version of IMDG, which is very very roughly targeted to early Q2 2021.

@brettcurtis
Copy link

Any update on this? I'd like to use a DNS name in my helm chart for

hazelcast.yaml.hazelcast.wan-replication.wanPublisherRegional.batch-publisher.regional-publisher.target-endpoints

@Holmistr
Copy link

@brettcurtis Actually yes! In recently released Hazelcast Platform 5.1, we've done many improvements with the usage of hostnames, especially around WAN replication. Could you give it a try and see if it works for your usecase? Hopefully it should.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants