Unless you use UUIDs it's hard to guarantees name uniqueness. For
instance, if there was a JGroups protocol which - before joining - sent
a broadcast to all members, asking whether the name it picked was
unique, and then joined, it would still not guarantee uniqueness. For
instance, if we are in a partitioned state, then a name picked might be
unique, but when a merge ensued later, we might discover that some other
member in a different partition has the same name.
On 5/3/12 5:14 PM, Thomas Fromm wrote:
Hi,
I've the requirement, that I need configurable cluster node names. These
names should be unique inside the cluster, new nodes with already
existing node names inside the cluster should be rejected to joind the
cluster and should fail at startup with an appropiate exception.
Additional, because I need these names in case of view events, something
like CacheManager.getNodeName(Address address)
Its a bit tricky to realise that using only the ISPN API, so I'd prefer
that could be done inside ISPN.
Is this change request possible for 5.2? What o you think?
--
Bela Ban, JGroups lead (
http://www.jgroups.org)