[
https://issues.jboss.org/browse/JGRP-1677?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1677:
--------------------------------
False alarm: MERGE3 doesn't get INFO messages from different clusters because
* The transport discards messages from different clusters
* If MPING or TCPPING is used, the PingHeader carries the cluster name and discards
messages from different clusters, too
MERGE3: discard traffic from different clusters
-----------------------------------------------
Key: JGRP-1677
URL:
https://issues.jboss.org/browse/JGRP-1677
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.4
When we have clusters one and two, if MERGE2 running in "one" gets an INFO
message from a node in "two", it doesn't discard it.
This could be the case when we use the TCP:TCPPING combo, and TCPPING.initial_hosts is
configured incorrectly, or we use PDC.
SOLUTION:
- Ship the cluster name in the MergeHeader and drop INFO messages from different clusters
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira