[
http://jira.jboss.com/jira/browse/JGRP-628?page=comments#action_12389766 ]
Bela Ban commented on JGRP-628:
-------------------------------
The algorithm is not incorrect: since discovery requests are *not* multicast through
MPING's multicast socket, but *unicast* back to the requester, they will get discarded
at the requester (since the cluster names don't match).
However, we'd like for discovery requests to not even get processed at the receivers
if the cluster names don't match, that's why cluster names will be added to
discovery requests
Discovery: add cluster name to discovery request to be able to
discard responses from different clusters
--------------------------------------------------------------------------------------------------------
Key: JGRP-628
URL:
http://jira.jboss.com/jira/browse/JGRP-628
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.7
When we have 2 groups ONE and TWO:
ONE: 228.8.8.8:7500 and
TWO: 228.1.2.3:7500
In some cases, they will receive each other's traffic
(
http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic).
Assume ONE has members {A,B,C} and TWO has no members yet. When D (in cluster TWO) starts
up and sends out a discovery request, it might also receive discovery responses from ONE
(A,B,C). D might now identify A as coordinator and send a JOIN-REQ to A. However, A will
discard that request as the group name of D's request is TWO rather than ONE !
Result: D's JOIN-REQ will hang !
Note that the transport (TP) does drop messages from different clusters, but this happens
only after the new member has joined the group, so discovery requests/responses from
different groups are *not* discarded.
Tasks:
- Verify that the transport-name matching algorithm in TP is correct
- Confirm that - on initial discovery - discovery requests and responses are not matched
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira