Re: [jgroups-users] using jgroups with multiple NICs

With UDP, you can make the MulticastSocket join the same multicast group 
on multiple interfaces, but a TCPsocket can only be bound to a given 
interface _once_.

The exception is to bind to the wildcard (0.0.0.0) interface, which 
makes the socket listen on *all* available NICs. However, this is not 
possible in JGroups, as we need to create a physical address consisting 
of the IP address of a NIC (e.g. 10.0.5.5) and a port (of the listening 
socket).

If they want failover, or load balancing, then I suggest they use some 
sort of link bundling (e.g. IP Bonding on Linux), which can be 
configured to do load balancing or failover.


On 14/11/18 9:09 PM, Questions/problems related to using JGroups wrote:
> Hi,
>
> Our product uses a TCP based stack, jgroups 4.0.13.Final. A customer
> has asked [sic below]:
>
> "how to tell the <my product> that "use both (or all) interfaces for
> <my product>-messaging"? We noticed that jgroups have this
> possibility. " I don't see how jgroups can use >1 bind address, i.e.
> because you can't send a tcp heartbeat request from more than one
> address (that would be >1 request).
>
> I *think* they want jgroups to monitor two separate networks (each
> node has 2 addresses, one for production and one for monitoring). If
> one network goes down then our product still sees that the other is
> running. We would need two separate channels for that, right?
>
> I know this all sounds simple, but am trying to wrap my head around
> what it is the customer wants. If I could share their slides that
> might help -- I think this is a 2 minute question except that I'm
> taking 10 minutes trying to explain it....
>
> Thanks
> Bobby
>
>
>
>
>
> _______________________________________________
> javagroups-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/javagroups-users

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)