[jboss-jira] [JBoss JIRA] Resolved: (JGRP-430) GossipRouter: support accessing multiple GossipRouters in TUNNEL
[
https://jira.jboss.org/jira/browse/JGRP-430?page=com.atlassian.jira.plugi...
]
Vladimir Blagojevic resolved JGRP-430.
--------------------------------------
Resolution: Done
Resolved, random stub approach is default. Pluggable interface provided for other/new
policies.
Commit set:
1.36 +8 -7 JGroups/src/org/jgroups/protocols/TCPGOSSIP.java
1.53 +21 -33 JGroups/src/org/jgroups/protocols/PING.java
1.58 +13 -7 JGroups/src/org/jgroups/protocols/TUNNEL.java
1.39 +19 -42 JGroups/src/org/jgroups/stack/RouterStub.java
A new test TUNNEL_Test2 has been added to test this functionality. Will be further
expanded!
GossipRouter: support accessing multiple GossipRouters in TUNNEL
----------------------------------------------------------------
Key: JGRP-430
URL: https://jira.jboss.org/jira/browse/JGRP-430
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.5
Reporter: Bela Ban
Assignee: Vladimir Blagojevic
Fix For: 2.8
Multiple GossipRouters can only be used for lookups, not for routing... However, since
all traffic to the GR goes out via TUNNEL (as JGroups transport), and TUNNEL uses a
RouterStub to send a message to the GR, we could do the following:
* the RouterStub is currently configured with the address of *one* GR
* a Stub.send() succeeds in connecting to the GR and sending the
message, or goes into a state where it tries to reconnect *forever*
* I could simply change that to configure the RouterStub with
multiple GRs:
o for send(), we iterate through the GRs until send() returns
true
EFFECT: a GossipRouter is not a single point of failure any longer
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira