Group Membership fails if Host runs as a domain name

[dbrimley]

If cluster members run in the cluster using their domain names and you have partition groups configured using IP addresses the cluster starts and then throws the following exception ....

“No member group is available to assign partition ownership"

It seems the code mandates using IP address for members and partition groups....

https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/partition/membergroup/ConfigMemberGroupFactory.java#L52

It would be useful if prior to this check a IP lookup was performed if the member is a domain name.

If this is not possible at least throw a more descriptive warning saying that you cannot mix domain name and ip address.

[pveentjer]

Using hostnames in HZ is a pain. Best to run with ip addresses.

[rjsalicco]

Is there a way to use a load balanced DNS entry to route to HZ instances during client or node startup for cluster discovery? For example:

<cluster-members>
            <!--initial cluster members to connect-->
            <address>cache.mycompany.com</address>
</cluster-members>

[mdogan]

@dbrimley: You can only use either an IP address or a domain name for a single member (at least currently this is how Hazelcast works).
Address (or domain name) is identity of the member in the cluster. If you mix IP and domain name for a member, then we need to do the same check/resolution on every place member's address is used.
For example, opposite of your setup should be valid too, configure members with IP addresses and partition groups with domain names.
To me this makes things very complicated but still can be considered as an enhancement.

[mahenderd2]

Is this issue resolved? seems it's long time issue is been open status

[Holmistr]

@mahenderd2 Unfortunately, there is currently no good resolution for this. It requires non-trivial effort to actually make it working with hostnames. There are plans to address that in future releases, but we have no specific plan as for now.