[
https://issues.jboss.org/browse/JGRP-2098?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2098:
--------------------------------
We could place {{NAMING}} over {{NAKACK2}} / {{UNICAST3}}, so we don't have to
implement our own reliability. To make things simple, the name cache would be populated as
follows:
* The joiner sends its address-name mapping to everyone after having joined successfully
* The joiner gets the full name cache from the coordintor, or - alternatively - everyone
sends its name to the joiner after the new view has been installed
Discovery: reduce messages when IpAddressUUID is used
-----------------------------------------------------
Key: JGRP-2098
URL:
https://issues.jboss.org/browse/JGRP-2098
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0
Attachments: LESS_PING.java
Since IpAddressUUID already contains the physical address, we don't need to exchange
physical addresses in the discovery phase.
Investigate whether this leads to reduced messaging in discovery, ie. only the coords
might send a response. Once the new member has the view, it automatically knows the IP
addresses and ports of all members, as the addresses in the view are of type
IpAddressUUID.
Also investigate whether address:logical_name associations should be done in a separate
protocol, e.g. NAMING.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)