[
https://issues.jboss.org/browse/JGRP-2098?page=com.atlassian.jira.plugin....
]
Neal Dillman commented on JGRP-2098:
------------------------------------
I believe that discovery should be limited to finding the coordinator. IP address
mapping, logical names, what have you, can all be put into a separate, optional protocol.
Further, I am not convinced that discovery is even really needed in the manner in which it
is currently done. For example, if one were to listen for sendInfo() messages from
MERGE3, one would be able to determine who the coordinator is and act upon that. In other
words, I believe we may wish to handle discovery as a byproduct of another protocol.
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
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)