-
Notifications
You must be signed in to change notification settings - Fork 87
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
Comments
@xrow , target endpoint, do you mean:
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 |
Can see hazelcast/hazelcast-enterprise#3627, but it sound like this is the one i am talking about. |
@xrow Just to make sure, so the issue is happening when you're using WAN replication? |
this is correct. |
@xrow I see, thank you. In that case, let me comment on it. |
Any update on this? I'd like to use a DNS name in my helm chart for
|
@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. |
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.
The text was updated successfully, but these errors were encountered: