[jboss-jira] [JBoss JIRA] (WFLY-1416) Cross site replication requires totally connected graph of sites/routes

Richard Achmatowicz (JIRA) jira-events at lists.jboss.org
Wed May 29 12:38:54 EDT 2013


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

Richard Achmatowicz edited comment on WFLY-1416 at 5/29/13 12:37 PM:
---------------------------------------------------------------------

Bela is looking to see if there is a non-performance impacting solution to this at the JGroups level. 

One AS level option would be to either:
(i) require a totally connected graph
(ii) if not totally connected, allow specifying site indices in XML with the remote-site element
 

                
      was (Author: rachmato):
    Bela is looking to see if there is a non-performance impacting solution to this at the JGroups level. 
One option would be to either:
(i) require a totally connected graph
(ii) if not totally connected, allow specifying site indices in XML with the remote-site element
 

                  
> Cross site replication requires totally connected graph of sites/routes 
> ------------------------------------------------------------------------
>
>                 Key: WFLY-1416
>                 URL: https://issues.jboss.org/browse/WFLY-1416
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 8.0.0.Alpha2
>            Reporter: Richard Achmatowicz
>            Assignee: Paul Ferraro
>
> Cross site replication is configured using JGroups subsystem <relay/> and <remote-site/> elements to define sites and multicast relay routes between sites. 
> Looking at a site/route configuration as a graph of nodes and edges, xsite only works if this graph is totally connected (i.e. every site has a defined direct route to every other site). This is because <site name> -> <site id> mappings are assigned per node, with no agreement on what is happening at other nodes.
> For example, this configuration works:
> <relay site="LON">
>   <remote-site name="NYC" .../>
>   <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
>   <remote-site name="LON" .../>
>   <remote-site name="SFO" .../>
> </relay>
> <relay site="SFO">
>   <remote-site name="NYC" .../>
>   <remote-site name="LON" .../>
> </relay>
> but this configuration does not:
> <relay site="LON">
>   <remote-site name="NYC" .../>
>   <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
>   <remote-site name="LON" .../>
> </relay>
> <relay site="SFO">
>   <remote-site name="LON" .../>
> </relay>

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


More information about the jboss-jira mailing list