[jboss-jira] [JBoss JIRA] (JGRP-2098) Discovery: reduce messages when IpAddressUUID is used

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288188#comment-13288188 ] 

Bela Ban commented on JGRP-2098:
--------------------------------

I attached LESS_PING instead of polluting the message stream here with code... :-)

Yes, the primary goal of discovery is finding the coordinator.

However, a second goal is also to discover all members out there in case of a merge. For instance, consider cluster A,B,C,D,E which falls apart into A,B and C,D,E on a split. Somehow, both sides need to find out who's out there when the network partition heals. MERGE3 delegates this to the discovery protocols as they already have the means of doing this. I don't want to copy this functionality into the merge protocol itself, to prevent duplication of code.

Re MERGE2 and sendInfo(): I don't want discovery to rely on another protocol. Some configs may not even have a merge protocol in it (I've seen that, although I think that's not correct). Also, some new merge protocols may not send an INFO message at all...

> 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)