[jboss-jira] [JBoss JIRA] (JGRP-1433) RELAY2: multi-site clustering

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1433:
--------------------------------

We probably still need virtual views: if we have LON={A,B,C} and SFO={X,Y,Z}, and want to invoke an RPC (from LON) to the target set (B,C,Y), the unicast RPC to Y would be discarded by the RequestCorrelator as it would note that the target Y is not in its view {A,B,C}. If we had a virtual view {A,B,C,X,Y,Z}, the call would pass correctly.

So perhaps having virtual views, but not relaying multicasts by default is the solution ?
                
> RELAY2: multi-site clustering
> -----------------------------
>
>                 Key: JGRP-1433
>                 URL: https://issues.jboss.org/browse/JGRP-1433
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.1
>
>
> Successor to RELAY. The biggest differences are:
> - Multicast messages are not relayed by default (has to be enabled in the protocol config, or per message (via flag))
> - Multiple sites can be connected, e.g. in a tree structure
> - There is no virtual view; every site gets the view for its local cluster. The application can fetch the view per site, or register for view notifications. There 1 view per site, e.g. "nyc": {A,B,C}, "sfo": {X,Y,Z} etc.
> The design is in docs/design/RELAY2.txt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira